Amos First is a narrative experiment that reframes early discovery within fast-moving teams. It emphasizes structured curiosity, rapid validation, and disciplined documentation from day one.
By treating initial insights as a repeatable process rather than a lucky moment, leaders can align stakeholders, reduce risk, and accelerate delivery.
| Phase | Goal | Key Action | Success Indicator |
|---|---|---|---|
| Observe | Surface real user behavior | Shadow users, capture raw data | 5+ contextual interviews completed |
| Hypothesize | Define a clear problem statement | Draft problem hypotheses | Hypotheses agreed by product and tech |
| Experiment | Test smallest viable change | Run constrained pilot or prototype | Measured signal supporting or refuting hypothesis |
| Document | Capture learnings for reuse | Log outcomes, decisions, and open questions | Artifact stored and linked to roadmap |
First Principles Discovery
Instead of copying patterns, Amos First pushes teams to question assumptions at the foundational level. This practice reveals constraints and opportunities that standard brainstorming often misses.
Each session strips away inherited biases and focuses on core needs, enabling original solutions rather than incremental tweaks.
Rapid Validation Cycles
Speed matters when insight can become obsolete quickly. Amos First turns early hypotheses into short experiments that deliver actionable feedback within days.
By limiting scope and using lightweight prototypes, teams maintain momentum while protecting resources.
Stakeholder Narrative
Leaders need a clear story to approve direction and allocate resources. Amos First structures early findings into a concise narrative that connects user pain to business outcomes.
Using simple visuals and plain language, teams secure buy-in without overpromising.
Execution Readiness
Insight is only valuable when it feeds execution. Amos First translates validated learning into prioritized workstreams, clarifying ownership, dependencies, and minimum viable scope.
Product and engineering collaborate on estimations, risk mitigations, and milestone checkpoints.
FAQ
Reader questions
Does Amos First replace existing discovery methods?
It complements and sharpens them by adding first-principles questioning and structured documentation that links insight to execution.
How long does a typical Amos First cycle take?
A focused cycle can range from one to three weeks, depending on problem complexity and access to users.
Who should own the Amos First process in a team?
Product leadership drives the process, but cross-functional contributors, including design, engineering, and data, share responsibility for outcomes.
What tools are recommended for documenting Amos First work?
Lightweight tools such as shared issue trackers, experiment boards, and living documents work best to keep artifacts accessible and traceable.