We avoid heavyweight methodology theater. The structure below is a baseline — we adapt ceremony to your team’s maturity, regulatory needs, and release frequency. What does not change: written decisions, visible backlog, and demos you can invite stakeholders to without embarrassment.
Phase 1 — Discovery & blueprint
Typical duration: 1–3 weeks depending on scope
- Stakeholder interviews and success metrics
- User journey mapping and technical constraints
- Competitive and channel landscape (for growth programs)
- Architecture options with risk and cost notes
- Written proposal: milestones, acceptance tests, and communication cadence
Phase 2 — Design & build
Typical duration: Varies — milestone-based
- UX flows and high-fidelity UI aligned to your brand
- Implementation sprints with weekly demos and shared task board
- Automated tests where ROI is clear; manual QA for critical paths
- Instrumentation: analytics events, error tracking, performance budgets
- Documentation for deploy, env vars, and runbooks
Phase 3 — Launch, measure, iterate
Typical duration: Ongoing or time-boxed
- Staged rollout, feature flags, and rollback plans
- SEO and performance verification on production
- Growth experiments with pre-registered hypotheses
- Weekly or biweekly reviews — spend, funnel, product blockers
- Roadmap grooming for the next cycle
Communication
Slack or Teams for day-to-day, email for formal approvals, and video for weekly demos. We maintain a single source of truth for tasks (your tool or ours) so status is not trapped in chat scrollback.
Change management
Scope changes happen — we capture them as written change requests with impact on timeline and cost. Small tweaks fold into the current sprint when reasonable; larger shifts are explicitly re-estimated so trust stays intact.