vault backup: 2026-08-07 15:57:47
This commit is contained in:
@@ -12,7 +12,7 @@ Operations remained stable, but several strategic projects slipped due to valida
|
||||
Traffic light: 🟡
|
||||
|
||||
This week's headline:
|
||||
|
||||
- Shifted from tracking execution to actively managing project commitments and accountability.
|
||||
|
||||
---
|
||||
|
||||
@@ -20,9 +20,11 @@ This week's headline:
|
||||
|
||||
Things that moved the company forward.
|
||||
|
||||
-
|
||||
-
|
||||
-
|
||||
- Successfully prepared and delivered the VP project portfolio presentation.
|
||||
- Established clearer expectations around project ownership, commitments, and operational coverage.
|
||||
- Continued building my long-term management system in Obsidian to centralize decisions, employee follow-ups, meetings, and projects.
|
||||
- Wrote a lot about solutions for a better Mogador and a Sync v2 which I'll call content publication engine (CPE)
|
||||
|
||||
|
||||
---
|
||||
|
||||
@@ -31,8 +33,10 @@ Things that moved the company forward.
|
||||
What keeps me awake?
|
||||
|
||||
| Risk | Impact | Mitigation | Owner |
|
||||
|------|--------|------------|-------|
|
||||
| | | | |
|
||||
| ---------------------------------------------------------------- | ------ | ------------------------------------------------------------ | ----- |
|
||||
| PBI Algolia delivery continues to slip after validation findings | High | Re-establish remaining work, validate against approved scope | Binta |
|
||||
| QA capacity reduced during Habiba's vacation | Medium | Reduce non-urgent requests and prioritize operational work | Me |
|
||||
| Operational coverage during Habiba, Valery and Joel vacation | Medium | Reduce non-urgent requests and prioritize operations | Me |
|
||||
|
||||
---
|
||||
|
||||
@@ -41,59 +45,65 @@ What keeps me awake?
|
||||
## Team health
|
||||
|
||||
Overall morale:
|
||||
🟢 High
|
||||
🟡 Normal
|
||||
🔴 Low
|
||||
|
||||
### Coaching / Recognition
|
||||
|
||||
Who deserves recognition?
|
||||
**Who deserves recognition?**
|
||||
|
||||
-
|
||||
- Habiba for identifying critical issues during validation instead of approving questionable results.
|
||||
- Slimane for continuing to move BetterStack monitoring forward despite shifting priorities.
|
||||
|
||||
Who needs coaching?
|
||||
**Who needs coaching?**
|
||||
|
||||
-
|
||||
- Binta on estimation, ownership, testing strategy, communication, and balancing project work with operational responsibilities.
|
||||
- Slimane More autonomy in prioritization and technical decision-making.
|
||||
|
||||
Any conflicts?
|
||||
**Any conflicts?**
|
||||
|
||||
-
|
||||
- Ongoing concerns regarding Algolia execution and expectations around project ownership for Binta. Hasn't done the "formation" from Ai Rei's jira ticket
|
||||
|
||||
Any hiring concerns?
|
||||
**Any hiring concerns?**
|
||||
|
||||
-
|
||||
- None this week.
|
||||
|
||||
---
|
||||
|
||||
# Projects 📁
|
||||
|
||||
| Project | Status | Next Milestone | Blocker |
|
||||
|----------|--------|----------------|----------|
|
||||
| | 🟢 | | |
|
||||
| | 🟡 | | |
|
||||
| | 🔴 | | |
|
||||
| ---------------------- | ------ | ----------------------------------- | ------------------------------- |
|
||||
| VP Portfolio | 🟢 | September follow up | None |
|
||||
| BetterStack Heartbeats | 🟡 | Selection and implementation | Operation takeover with tickets |
|
||||
| Umami | 🟡 | Establish new timeline | Operation then vacations |
|
||||
| FMC | 🟢<br> | First draft as to what is available | None |
|
||||
|
||||
Projects slipping:
|
||||
|
||||
-
|
||||
- Algolia
|
||||
- Umami
|
||||
- Monitor Mogador
|
||||
|
||||
Projects completed:
|
||||
|
||||
-
|
||||
- VP portfolio presentation
|
||||
|
||||
---
|
||||
|
||||
# Vendors 🤝
|
||||
|
||||
Any issue?
|
||||
- Important discussion regarding advertisement placement requiring follow-up Mediatonik
|
||||
- Trings is asking $3500 for tags which I'll approve
|
||||
|
||||
Renewals coming?
|
||||
- None
|
||||
|
||||
Invoices pending?
|
||||
- None handled the ones from Affranchis and Libeo
|
||||
|
||||
Contract risks?
|
||||
|
||||
-
|
||||
- None
|
||||
|
||||
---
|
||||
|
||||
@@ -101,11 +111,9 @@ Contract risks?
|
||||
|
||||
Important numbers this week.
|
||||
|
||||
-
|
||||
|
||||
-
|
||||
|
||||
-
|
||||
- No formal KPI review.
|
||||
- Main focus remained project execution and delivery.
|
||||
- Executive visibility into project portfolio improved.
|
||||
|
||||
Anything unusual?
|
||||
|
||||
@@ -115,9 +123,10 @@ Anything unusual?
|
||||
|
||||
# Decisions Made
|
||||
|
||||
Decision | Why
|
||||
---------|----
|
||||
| |
|
||||
| Decision | Why |
|
||||
| ---------------------------------------------------------- | ------------------------- |
|
||||
| Prioritize Board of Directors work over Algolia validation | Executive priority |
|
||||
| Will pay $3500 extra to trings for tags | Keeping the OTT in french |
|
||||
|
||||
---
|
||||
|
||||
@@ -125,8 +134,7 @@ Decision | Why
|
||||
|
||||
What decisions must be made next week?
|
||||
|
||||
-
|
||||
|
||||
- Do we need a 2nd streams for the live on the OTT
|
||||
-
|
||||
|
||||
---
|
||||
@@ -135,7 +143,8 @@ What decisions must be made next week?
|
||||
|
||||
Which meetings created value?
|
||||
|
||||
-
|
||||
- Sprint review
|
||||
- Meeting with JC about the live POC and streamin
|
||||
|
||||
Which meetings should disappear?
|
||||
|
||||
@@ -154,11 +163,12 @@ Which meetings could become:
|
||||
|
||||
What did I unnecessarily do myself?
|
||||
|
||||
-
|
||||
- Anything mogador
|
||||
|
||||
What should be delegated next week?
|
||||
|
||||
-
|
||||
- Anything Idello
|
||||
- Continue delegating technical execution while focusing on commitments, priorities, and outcomes.
|
||||
|
||||
---
|
||||
|
||||
@@ -172,7 +182,9 @@ Podcasts
|
||||
|
||||
Lessons learned
|
||||
|
||||
-
|
||||
- Validation should confirm quality, not discover fundamental defects.
|
||||
- Approved project documents should not be modified without communication.
|
||||
- A manager's role is to manage commitments and decisions rather than solve technical problems.
|
||||
|
||||
---
|
||||
|
||||
@@ -180,9 +192,16 @@ Lessons learned
|
||||
|
||||
Something that annoyed me this week.
|
||||
|
||||
|
||||
|
||||
- Important project documentation was modified after approval without notification.
|
||||
|
||||
How can I make sure it never happens again?
|
||||
|
||||
-
|
||||
- Require communication whenever approved project documentation changes.
|
||||
- Continue formalizing project governance and documentation practices.
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
@@ -190,37 +209,41 @@ How can I make sure it never happens again?
|
||||
|
||||
If the CEO walked in Monday morning, what questions might they ask?
|
||||
|
||||
1.
|
||||
|
||||
2.
|
||||
|
||||
3.
|
||||
- When will Algolia actually be completed?
|
||||
- What projects are currently at risk?
|
||||
- Are we properly staffed for upcoming priorities?
|
||||
|
||||
Do I already know the answers?
|
||||
Yes
|
||||
|
||||
---
|
||||
|
||||
# Top Priorities Next Week
|
||||
|
||||
1.
|
||||
1. Review Binta's tickets and delivery of the FMC project
|
||||
|
||||
2.
|
||||
2. See if Affranchis has a solution for the sync issues
|
||||
|
||||
3.
|
||||
3. Start talking about CPE.
|
||||
|
||||
---
|
||||
|
||||
# Personal Reflection
|
||||
|
||||
Energy (1-10):
|
||||
Energy (1-10): 8
|
||||
|
||||
Stress (1-10):
|
||||
Stress (1-10): 4
|
||||
|
||||
Biggest accomplishment:
|
||||
Biggest accomplishment: Mogador and preparing the presentation for the VP
|
||||
|
||||
Biggest mistake:
|
||||
- Not following closely Binta
|
||||
- Not establishing earlier expectations around documentation governance and operational/project balancing.
|
||||
|
||||
One thing to improve next week:
|
||||
- Ask better question
|
||||
- Do more follow up
|
||||
- Ask for documentation
|
||||
|
||||
---
|
||||
|
||||
@@ -235,30 +258,33 @@ Random ideas to revisit later.
|
||||
|
||||
# CTO Development
|
||||
|
||||
Leadership
|
||||
### Leadership
|
||||
|
||||
-
|
||||
- Improved documentation of employee performance and coaching discussions.
|
||||
- Strengthened expectations around ownership and commitments.
|
||||
|
||||
Technology
|
||||
### Technology
|
||||
|
||||
-
|
||||
- Continued refining the Obsidian knowledge system.
|
||||
- Advanced BetterStack monitoring planning.
|
||||
|
||||
Business
|
||||
### Business
|
||||
|
||||
-
|
||||
- Improved executive project portfolio reporting.
|
||||
- Better understanding of project governance.
|
||||
|
||||
Finance
|
||||
### Finance
|
||||
|
||||
-
|
||||
- Continued discussions around vendor and project prioritization.
|
||||
|
||||
Communication
|
||||
### Communication
|
||||
|
||||
-
|
||||
- More direct conversations around expectations while remaining fact-based.
|
||||
|
||||
One thing I did this week that made me more like a CTO:
|
||||
**One thing I did this week that made me more like a CTO:**
|
||||
|
||||
-
|
||||
- Focused on governance, prioritization, accountability, and executive visibility rather than technical implementation.
|
||||
|
||||
One thing I did this week that kept me acting like an individual contributor:
|
||||
**One thing I did this week that kept me acting like an individual contributor:**
|
||||
|
||||
-
|
||||
- Spent too much time personally investigating technical details and documentation changes instead of relying on project ownership and management processes.
|
||||
|
||||
Reference in New Issue
Block a user