Delivered on time, by a team that knows its job.

Eight phases, two weeks each as a baseline. App work runs in sprints, with design one sprint ahead of the build.

Schedule a Meeting

WHO IT'S FOR

  • —  Teams that need a schedule they can trust.
  • —  Products with many moving parts — configurators, apps, brand systems.
  • —  Clients who want to see progress every two weeks.

THE PHASES

Start, stay on course, finish with flying colors.

STARTSTAY ON COURSEFINISH WITH FLYING COLORS
ORGANIZED, START TO FINISHShared folders, requirements written down, a structure ready on day one. Nobody hunting, nobody waiting.
01DiscoveryGather infofrom the brief.02ResearchDiscover beforesketch.03DirectionImagine theright path forward.04DesignOrganize &Create05RefineIt’s all inthe Details.06DeliveryCheck EVERYcomponent07DevelopDive in, or be theCreative Guide08OngoingTeam success beyondlaunch, not the endand round again —the next version

01

Discovery

●●○ standard

Every job

  • —  The kickoff conversation: goals, audience, budget, the date that can't move
  • —  Who signs off, and who else has a say
  • —  Competitive comparison — who else is out there, and how they look and work
  • —  What already exists: files, past work, what worked and what didn't

You get: a one-page brief we both sign off

ORGANIZED, START TO FINISHShared folders, requirements written down, a structure ready on day one. Nobody hunting, nobody waiting.
START
01
Discovery
Gather info from the brief.

01

Discovery

●●○ standard

Every job

  • —  The kickoff conversation: goals, audience, budget, the date that can't move
  • —  Who signs off, and who else has a say
  • —  Competitive comparison — who else is out there, and how they look and work
  • —  What already exists: files, past work, what worked and what didn't

You get: a one-page brief we both sign off

02
Research
Discover before sketch.
STAY ON COURSE
03
Direction
Imagine the right path forward.
04
Design
Organize & Create
05
Refine
It’s all in the Details.
FINISH WITH FLYING COLORS
06
Delivery
Check EVERY component
07
Develop
Dive in, or be the Creative Guide
08
Ongoing
Team success beyond launch, not the end
↺  and round again — the next version

TIMING

Sixteen weeks, start to launch — as a baseline.

  1. 01Weeks 1–2
  2. 02Weeks 3–4
  3. 03Weeks 5–6
  4. 04Weeks 7–8
  5. 05Weeks 9–10
  6. 06Weeks 11–12
  7. 07Weeks 13–14
  8. 08Weeks 15–16

Baseline: 2 weeks per phase. Real lengths per kind of work come later.

SPRINTS

Design runs one sprint ahead of the build.

Design
  1. Sprint 1
  2. Sprint 2
  3. Sprint 3
  4. Sprint 4
Build
  1. Sprint 1
  2. Sprint 2
  3. Sprint 3
  4. Sprint 4

THE X-FACTOR

Design runs flat out first. Then the build does.

Early on, design is at full throttle — delivering everything every team needs — while development ramps up. We meet in the middle, and that's where handoff begins. From there the developers are busiest and design throttles back. Both stay in it, start to finish.

Effort over the eight phases: Creative — full throttle; Development — ramping up; Handoff begins; Development — busiest; Creative — throttled back, still in it; — Creative; - - DevelopmentCreative effort starts high and eases; development starts low and peaks after handoff

HOW THE TEAM WORKS

Three ways I work — every project uses one.

ROLES

  • —  Design lead — me: direction, reviews, and I still design
  • —  Designers
  • —  Developers

RHYTHM

  • —  Kickoff
  • —  Weekly touch points
  • —  Demo at the end of every sprint

Proof: Ford (team of 10+) · Fire Dispatch (team of 2) · Beans for a Cause (solo) →

HOW IT WORKS

Four steps to week one.

  1. 1Schedule a meeting
  2. 2Scope the work together
  3. 3Confirm and sign
  4. 4Kickoff — week one starts

PROOF

On time, on real projects.