Most project managers are not running 200-person programmes. Most are running small teams with tight budgets, fewer people than they need and a deadline that has not moved. The operating model is closer to a small studio than to a matrixed enterprise.
Designer Jeff Sheldon built Ugmonk as a side project with no budget, then grew it over a decade while keeping the team lean. The discipline of doing more with less is not a phase to outgrow; it is the operating system.
At a glance
- Ugmonk is a design brand built on simplicity and minimalism, founded by Jeff Sheldon.
- Sheldon has run the business for about 10 years while keeping overhead low.
- He works from a home office and handles design, writing and product photography himself.
- He has no outside investors and no quarterly growth targets.
- His personal productivity tool is a paper card with a small daily task list.
Why small is a feature
Sheldon's argument is not that small teams are scrappy by default; it is that small teams have optionality that larger ones do not. No investors means no quarterly growth target means he can take a week off when his family needs him. No big infrastructure means he can ship a new product line without a steering committee. The freedom to choose what to work on, and when, is itself a competitive advantage.
For project managers this lands close to home. A small team can reprioritise a sprint in a morning. A large programme needs a change control board, two meetings and a memo. The smaller team's speed is its edge, and anything that erodes that speed is a real cost.
The "do a lot with a little" discipline
Doing a lot with a little is not the same as doing a lot with nothing. Sheldon describes using off-the-shelf tools, a home office and DIY processes. The discipline is in the choices: which tools, which processes, which meetings. Each one has to earn its place.
For a project manager, this maps to ceremony hygiene. Stand-ups, retros, planning sessions and demos are useful. Status reports nobody reads, steering committees that decide nothing and risk registers nobody updates are not. The lean move is to cut the second category without flinching.
Work-life integration, not balance
Sheldon is honest about a point most leadership advice glosses over: for a small-team operator, work and life are not separated. The skill is not finding balance; it is staying aware of how much work is crowding out the rest. For him that means being present with family when with family, and present with work when at work. The half-and-half version of both is the worst outcome.
For project managers this is a familiar tension. On-call rotations, late deploys and sprint reviews bleed into evenings. The professional answer is to set boundaries; the honest answer is that boundaries are negotiable during crunch and rigid outside it. Knowing which mode you are in, and telling the team, is the real skill.
Our analysis
The Ugmonk story is a useful counterweight to enterprise thinking. Most project management advice assumes you have more people, more budget and more time than you actually do. The lean-team playbook is closer to day-to-day reality for most PMs.
The core trade-off is growth versus autonomy. Sheldon chose autonomy—he does not have to hit investor numbers, but he also does not have investor money. For a project manager, the equivalent choice is between a heavily-governed programme with a big budget and a small team with a thin mandate. The first looks impressive on a CV; the second moves faster and lets you shape the work. Both are legitimate. The point is to know which one you are picking and why.
Who wins with lean? Teams that need to iterate fast, respond to user feedback and maintain quality without process overhead. Who loses? Teams that mistake ceremony for professionalism, adding stand-ups because a book recommended them, not because the work needed them. The danger is symmetric: a lean team that refuses to add process even when the team grows and needs it, just as much as an enterprise team drowning in governance that nobody questions.
What to watch next
Watch for the small ceremony that nobody questions. That is usually the first thing to cut. Watch for the process that exists because someone read about it, not because the team needs it. And watch for the lean team's bad habit of refusing to add process even when the team grows and starts to need it. Lean is not the same as under-resourced. The discipline is in choosing which constraints you keep and which you outgrow.
Who should care
| Role | Why it matters |
|---|---|
| Project managers running small teams | Lean discipline keeps overhead low and speed high—your actual competitive edge |
| Agile coaches | The Ugmonk logic mirrors backlog hygiene: cut what does not earn its place |
| Founders and small-team leaders | Sheldon's autonomy choice is replicable; the trade-off is explicit |
| Programme managers moving to smaller scopes | The speed advantage of small teams is real; protect it, do not replicate enterprise habits |
Key takeaways
- Small teams have optionality that larger ones lose; protect it.
- Every meeting, report and register needs to earn its place.
- Work-life integration is the honest frame; pick the mode and tell the team.
- Lean is a choice, not a budget. Revisit it when the team grows.
- The trade-off between growth and autonomy is explicit—know which one you are choosing.
Frequently asked questions
Who is Jeff Sheldon?
He is the founder of Ugmonk, a design brand he has run for about 10 years while keeping the team and overhead small.
What is the "do a lot with a little" philosophy?
It means choosing tools, processes and overhead deliberately so each one earns its place, instead of adding layers because they feel professional.
How does a small team stay productive?
By keeping task lists short, cutting unnecessary meetings and using simple tools that fit the work—including paper-based systems.
What can project managers learn from a small design brand?
That overhead is a choice, ceremonies need to earn their place, and lean teams win on speed and optionality, not on size.
Does lean mean under-resourced?
No. Lean is a discipline of cutting what does not earn its place; under-resourced is a budget problem. The two often get confused.