vault backup: 2026-07-27 17:27:02

.obsidian/plugins/editing-toolbar/data.json

@@ -404,7 +404,7 @@
   "cMenuNumRows": 12,
   "cMenuWidth": 610,
   "cMenuFontColor": "#2DC26B",
-  "cMenuBackgroundColor": "#d3f8b6",
+  "cMenuBackgroundColor": "#ff4d4f",
   "autohide": false,
   "Iscentered": false,
   "custom_bg1": "#FFB78B8C",

10 Knowledge/Templates/Journal Template.md

@@ -1,5 +1,12 @@
 # {{date}}
 
+## Legend 
+🟢 On Track / Healthy 
+🟡 Attention 
+🟠 At Risk 
+🔴 Critical / Off Track 
+⚪ Unknown
+
 ## What Happened
 
 - 

10 Knowledge/Templates/Project Template.md

@@ -5,7 +5,7 @@
 - 🟠 **At risk**: intervention/decision required or commitment is likely to slip
 - 🔴 **Critical / Off track**: commitment missed, major blocker, or immediate intervention required
 - ⚪ **Unknown**: insufficient information to assess
-- 
+
 **Status:** 🟢 Active
 **Owner:** 
 **Start Date:** {{date}}

20 Work/Journal/2026-07-27.md

@@ -0,0 +1,52 @@
+## What Happened
+
+### Projects 
+- 🟡 **Umami** - Dates need replanning 
+- 🟠 **Algolia** - Jalon 2 not validated, delivery due July 28 
+- 🟢 Hub - Going great but ads must be clarified as to what will be delivered
+
+### Operations - 
+- ⚪ **Jira SLA health** - Visibility currently insufficient 
+- 🟠 **Habiba coverage** - Vacation Friday, coverage needs clarification 
+
+### Capacity 
+- 🟠 **QA** - Four projects approaching QA, freelancer not possible until January 
+
+### Upcoming 
+- 🟢 **VP September Review** - Projects + operations, team participating 
+
+## CTO 1-1 
+- Freelancer QA: CTO agrees with approach, January earliest 
+- Strategic KPI initiative: CTO agrees with direction 
+- VP wants team project review in September
+
+
+## Notes
+
+### September - VP Project Portfolio Review
+
+CTO informed me that VP wants a review of the team's projects in September.
+
+**Expected:**
+- Projects currently being worked on
+- Current status / progress
+- Team members present
+- Team participation in presenting/discussing their work
+
+**Implication**
+
+Monday needs to accurately reflect the project portfolio before this meeting.
+
+Project owners need to be comfortable explaining:
+- What are we trying to accomplish?
+- Where are we?
+- What is the next commitment?
+- When will it be delivered?
+- What is blocking us?
+
+
+**Next steps**
+- Clean up project portfolio in Monday.
+- Establish regular project-owner updates.
+- Determine September presentation format.
+- Prepare team before VP review.

20 Work/Team/Binta.md

@@ -92,4 +92,20 @@ Binta a répondu à ce commentaire à 11:16.
 - Échanges concernant le nouvel échéancier
 
 ### Modification du cadrage après validation 
-Le document de cadrage approuvé a été modifié les 26 et 27 juillet. Binta a confirmé que le document avait été modifié. Elle a expliqué que les ajouts provenaient de constats effectués pendant la validation des volumes prévue au Jalon 2. Il lui a été demandé de notifier l'équipe lorsqu'un document déjà validé est modifié afin d'éviter toute confusion. Binta a confirmé avoir compris la demande. À vérifier lors de la validation du Jalon 2 : - Les nouvelles règles documentent-elles simplement des limitations découvertes pendant les tests? - Modifient-elles les critères d'acceptation précédemment convenus? - Les écarts qu'elles expliquent avaient-ils été identifiés avant ou après leur ajout au document?
+Le document de cadrage approuvé a été modifié les 26 et 27 juillet. Binta a confirmé que le document avait été modifié. Elle a expliqué que les ajouts provenaient de constats effectués pendant la validation des volumes prévue au Jalon 2. Il lui a été demandé de notifier l'équipe lorsqu'un document déjà validé est modifié afin d'éviter toute confusion. Binta a confirmé avoir compris la demande. À vérifier lors de la validation du Jalon 2 : - Les nouvelles règles documentent-elles simplement des limitations découvertes pendant les tests? - Modifient-elles les critères d'acceptation précédemment convenus? - Les écarts qu'elles expliquent avaient-ils été identifiés avant ou après leur ajout au document?
+
+## <mark style="background:#ff4d4f">Operational ticket capacity</mark>
+
+Habiba informed me that she asked Binta to take operational tickets.
+
+According to Habiba, Binta indicated that she would only take tickets if they did not affect her project deadline and did not agree to take the requested work.
+
+Habiba indicated that Binta did not propose discussing/reprioritizing the requested delivery with the ticket owner.
+
+Habiba will be on vacation for two weeks beginning Friday, which will reduce available coverage for these operational requests.
+
+### To clarify
+
+- Confirm expected operational coverage while Habiba is absent.
+- Clarify with Binta that project commitments and operational responsibilities must be balanced according to management/team priorities.
+- Establish who will cover Habiba's tickets during her absence.

20 Work/Team/Joel.md

@@ -0,0 +1,77 @@
+
+## Role
+
+**Position:** Integrator
+**Responsibilities:** 
+
+## Current Objectives
+
+- Stabilize Sync
+- Lead internal team
+- 
+
+## Current Projects
+
+- Umami
+- Sync Mogador
+
+## 1:1 Notes
+
+### 2026-07-27
+
+**Topics discussed:**
+
+- Google Ads
+	- Les Affranchis ont changé le ad.txt (sur staging), attente d'approbation de Google ad.txt. Ils veulent un lecteur JWP dedié pour les pubs et un autre lecteur pour ne pas avoir de pub. Il y a un risque.
+- Umami
+	- Revoir les dates de projets. Dé
+
+**Employee feedback / concerns:**
+
+- 
+
+**My feedback:**
+
+- 
+
+**Agreed actions:**
+
+- [ ] 
+
+## Performance Observations
+
+### 2026-07-27
+
+**Situation:**
+
+**Expected outcome:**
+
+**Actual outcome:**
+
+**Impact:**
+
+**Follow-up:**
+
+## Development
+
+### Strengths
+
+- 
+
+### Areas for Development
+
+- 
+
+### Support / Coaching Provided
+
+- 
+
+## Commitments
+
+| Commitment | Owner | Due | Status |
+|---|---|---|---|
+| | | | |
+
+## Related
+
+- [[]]

20 Work/Weekly Review/Jira Review.md

@@ -1,7 +1,7 @@
 
 2026-07-27
 
-HAE -> 7 en cours 2 en attente
+HAB -> 7 en cours 2 en attente
 Binta -> 2 en cours 1 en attente
 JC -> 9 en cours 1 en attente
 JY -> 4 en cours 1 en attente

20 Work/Weekly Review/Weekly Review - 2026-07-27.md

@@ -1,63 +0,0 @@
-## Risks / Attention
-
-### QA capacity - upcoming projects
-**Status:** 🔴 High
-
-Four major projects are expected to reach QA close together.
-
-Current QA capacity: 1 person.
-
-**Risk:** QA becomes a bottleneck, delaying project delivery even if development finishes on schedule.
-
-**Proposed mitigation:** Temporary freelance QA support during the overlapping QA period.
-
-**Discuss with CTO:** 2026-07-27
-
-**Next step:** 
-- [ ] Determine how to manage QA capacity for September.
-- [ ] Get everything ready for ideally November so that in January, freelancer is ready
-
-Related
-https://docs.google.com/presentation/d/1Eg588k87Bxsy_pTxxjc-xPuXfEiFMFJbqP3FD0FCvgg/edit?slide=id.g3db66fc5ba7_0_2#slide=id.g3db66fc5ba7_0_2
-
-----
-### September - VP Project Portfolio Review
-
-CTO informed me that VP wants a review of the team's projects in September.
-
-**Expected:**
-- Projects currently being worked on
-- Current status / progress
-- Team members present
-- Team participation in presenting/discussing their work
-
-**Implication**
-
-Monday needs to accurately reflect the project portfolio before this meeting.
-
-Project owners need to be comfortable explaining:
-- What are we trying to accomplish?
-- Where are we?
-- What is the next commitment?
-- When will it be delivered?
-- What is blocking us?
-
-
-**Next steps**
-- Clean up project portfolio in Monday.
-- Establish regular project-owner updates.
-- Determine September presentation format.
-- Prepare team before VP review.
-
-----
-### 🟡 Umami
-
-No progress during my two-week absence.
-
-Project owner was reassigned to stabilization/fixes of website synchronization code.
-
-Owner leaves on vacation Friday. When he returns, I will be on vacation.
-
-**Impact:** Existing Umami dates are no longer realistic.
-
-**Next:** Owner and I need to establish a new project timeline.