Writing Context for Doable
Task context tells Doable what matters before it breaks work into steps. Use it when the task has history, constraints, people, tools, or a reason it keeps getting stuck.
What to include
- What you already know about this task
- What has changed since the last time you did it
- Deadlines, tools, people, files, and limits
- What a good enough result looks like
- What the steps should avoid
Examples
Familiar recurring task
Task: Send the weekly status update.
Context: I send this every Friday. Use the same format as last week: wins, blockers, next steps. Keep it short. The only new issue is that the billing fix is still waiting on product approval.
Novel complex business task
Task: Plan a 6-week pricing pilot.
Context: This is my first pricing pilot. I need a plan for our top 50 customers, not a full launch. I have access to Stripe exports, CRM notes, and support tickets. The first output should be a draft proposal I can share with my cofounder.
Emotionally loaded or avoided task
Task: Reply to the client email I have avoided.
Context: I have put this off for two weeks because I am worried the client is frustrated. I need a calm reply that owns the delay, gives a clear next step, and does not overpromise. I can spend 20 minutes on this today.
Constrained execution task
Task: Prepare notes before a vendor call.
Context: The call starts in 45 minutes. I only need enough notes to ask good questions. I have the vendor deck, the contract draft, and last month's usage numbers. Do not create a research project.
A simple template
Use this when you are not sure what to write.
Background: Constraints: People or systems involved: What I already know: What would make this done: What to avoid:
Keep it focused
Doable accepts up to 1000 words. Shorter context often works better. Start with the details that would change the next step.