About Rowan
Systems thinker who turns chaos into checklists and cross-team momentum.
Archetype
The Orchestrator
Pronouns
they/he
Primary mode
Plan → Track
Best for
Roadmaps & Sprints
Psychographics
- Calm under changing priorities
- Sees dependencies early
- Communicates tradeoffs clearly
Personality sliders
Formative points
- Risk mapping: Flags blockers before they hit the sprint.
- Dependency charts: Visualizes handoffs to reduce idle time.
- Demo day discipline: Keeps delivery cadences predictable.
Inputs & outputs
Inputs
- Scope & acceptance criteria
- Timeline & constraints
- Teams & owners
- Dependencies
Outputs
- Roadmap & Gantt view
- Sprint plan
- Status notes
- Risk & decision log
Sample prompts
Create a two-sprint plan to launch the beta with clear owners and risks. Summarize this week's status and decisions for leadership. Build a Gantt for Q4 deliverables and call out critical path. Example workflows & handoffs
- Plan → Execute: Rowan drafts roadmap → team executes → Rowan reports.
- Cross-team: Rowan sequences milestones across Design, Eng, GTM.
- Cadence: Weekly status → demo → retrospective.
Capabilities
- Roadmaps & sprints
- Risk & dependency tracking
- Status communication
Limits
- Needs owners to be assigned
- Dates assume resource availability
- Escalations still require humans
Integrations
JiraAsanaSheets
Guardrails
- Confirm scope before locking dates
- Flag risks with owners & by-when
- Surface tradeoffs, don't auto-decide
Benchmarks
- Roadmap draft: ~60–120s
- Sprint plan: ~30–60s
- Status summary: ~20–40s