2 min lesson
Day-30 / 60 / 90 mental model
Choose two examples from the table in "Day-30 / 60 / 90 mental model" and explain what each teaches you to do.
Step 1 of 2
The hiring manager will probe whether you can turn an ambiguous mandate into a concrete plan. Have a 30/60/90 ready and anchor every milestone in toil removed rather than tools touched.
Start from the bar Cursor actually sets. This is a small, flat, talent-dense team and the expectation is a functioning senior IC who ships from week one, not a junior who ramps for a quarter. Your plan should open with something shipped, not something studied.
- Horizon
- Week one
- Focus
- Ship
- Concrete outcome
- A small, real improvement live - earn trust by producing, not just learning
- Horizon
- Day 30
- Focus
- Map + find impact
- Concrete outcome
- The existing GTM stack mapped; the highest-toil friction identified with data
- Horizon
- Day 60
- Focus
- Build + instrument
- Concrete outcome
- A reusable workflow or agent shipped, with a feedback loop measuring it
- Horizon
- Day 90
- Focus
- Generalize
- Concrete outcome
- A program primitive adopted by another team, segment or program
| Horizon | Focus | Concrete outcome |
|---|---|---|
| Week one | Ship | A small, real improvement live - earn trust by producing, not just learning |
| Day 30 | Map + find impact | The existing GTM stack mapped; the highest-toil friction identified with data |
| Day 60 | Build + instrument | A reusable workflow or agent shipped, with a feedback loop measuring it |
| Day 90 | Generalize | A program primitive adopted by another team, segment or program |
The arc moves from one shipped fix to a primitive others reuse - impact compounding over the quarter.
Day 30 is reconnaissance with a deliverable. You map how data flows today, where the manual handoffs are and which workflow burns the most human hours. The output isn't a doc for its own sake; it's a ranked list of friction with the most impactful target named and quantified.
- 1Map the stack. Inventory the tools, integrations and data flows that exist, including the undocumented Zaps and spreadsheets.
- 2Quantify the toil. Find where humans copy-paste, reconcile or manually route - and put hours or error rates on it.
- 3Pick the wedge. Name the one workflow whose automation buys the most time or removes the most risk and say why.