Meta fwks
As entrepreneur, you better ask questions.
All day.
And get proefficient at it, because the quality of the replies is limited by the qality of the questions.
Communication Patterns
Stop moving information and adding some noise in the process.
Start driving outcomes across teams, programs, and the broader organization.
I put together a detailed framework in this blog section
| Business situation | Recommended pattern | Target outcome |
|---|---|---|
| Bug / root cause analysis | DFIR: Investigation | Establish facts and suggest recommendations. |
| Release status / multi-issue sync | COAST: Alignment Sync | Define ownership and next triggers. |
| Approvals / chasing deliverables | DRIVE: Follow-Up and Execution | Get a fast, frictionless response. |
| Designing future solutions | ADAPT: Architecture and Decision | Reach a decision on the technical path forward. |
| Handoff to an upstream team | FACT: Cross-Team Handoff | Move ownership without assumptions. |
| Multi-system diagnostic | TRACE: Complex Technical Investigation | Keep technical teams focused on data evidence. |
Fwk details 📌
Although each framework serves a different purpose, they all answer the same five stakeholder questions:
- What happened? (Context)
- What do we know? (Evidence)
- Who owns it? (Accountability)
- What decision is needed? (Action)
- What happens next? (Trigger)
Converging vs Diverging 📌
Sync vs Async 📌
Logic
Unit Economics