Eat the elephant one bite at a time

When a team freezes in front of something huge, like a payments rebuild, a migration or a new platform, the cause is rarely motivation or talent. Usually nobody can see where to start, so the work sits there and looks more daunting every week.

What helps at that point is finding a first slice small enough to ship this week, getting it live and showing the team the rest is achievable.

Cut the work so each piece is useful by itself, instead of being a fraction of a distant finish line. Ship split payments, then vouchers, then deposits. Each is valuable on its own, and each makes the next easier because the foundations already exist.

After a year of working like that, you've built something large without ever taking it on in one go.

A six-month project can be "on track" right up until the day it isn't. A sequence of weekly slices can't hide problems: either this week's piece shipped or it didn't.

Working in small pieces means you find out you're in trouble early, while it's cheap to correct, instead of at the end when it's expensive and public.

Designing the whole programme before shipping anything feels responsible, but it's often a way of putting off the scary part.

A team will learn more from shipping the first real slice than from any amount of planning up front, because real use shows things a plan can't. Ship the first piece and let what you learn reshape the rest.

The goal is a team that breaks big things down without being told, and that responds to a daunting brief by asking "what's the smallest useful first slice?" instead of "how long will the whole thing take?"

Once the whole team works that way, nothing on the roadmap is too big to start.