A specific failure mode I've watched unfold multiple times, more than once: a small team of talented engineers, each holding a demanding role elsewhere, agrees to build something ambitious together. Everyone's excited. The project fails. Not because of skill or planning, but because inspiration-driven work needs sustained attention, and no one on the team has any to give.
This is not a comment on the people. They were good. It's a comment on team composition versus product type.
Some products can be built by a competent part-time team. CRUD apps, integrations, well-scoped tools, replacements for known workflows. The requirements are clear. The design space is small. Moderate attention across evenings and weekends is enough.
Other products cannot be built this way. Anything that requires a coherent creative vision, a novel interaction model, or a non-obvious insight needs someone whose primary attention is on it. Full-time attention isn't about hours worked. It's about mental space. A person doing a demanding day job doesn't have the mental space to be inspired about something else, no matter how much they want to be.
Busy technocrats will contribute code. They will not contribute insight, because insight requires the slack that a full-time job consumes.
The practical rule:
Match team composition to product type. If your product needs inspiration, someone on the team needs the space to be inspired. If everyone on the team is holding down a demanding role elsewhere, the product you can actually build is the one that doesn't need inspiration.
Both are legitimate products. The mistake is committing to an inspiration-heavy vision with a team structurally unable to supply the inspiration.
For anyone assembling a part-time team right now: ask honestly whether the ambition of the project matches the attention the team can commit. If it doesn't, either scale down the ambition or restructure the team. Doing neither is the standard, expensive mistake.
Drafted in January 2023
Updated for site in 2026