Projects are delivered by people.

It took us a long time to see something that, looking back, was always in plain sight.

This is the story of how we got here, and what we learned along the way.

---

01 · Where we began

In the engine room

We started where the data lives. Pipelines, models and warehouses: the quiet engineering beneath every report a board ever reads.

It was rewarding work. Data, given the right structure, behaves. Ask it a clear question and it answers the same way every time.

The projects around it were another matter. Good engineering was landing late, or not landing at all, and the reasons rarely had anything to do with the code.

So we went looking for the reasons.

02 · Learning the craft

Running the project, not just building it

That search led us into project management. We stayed close to what we knew, delivering data projects, but now we were the ones holding the plan, the budget, the risks and the room.

We learned the disciplines properly. Waterfall where certainty matters, Agile where it doesn’t, and a blend of the two for most of real life. Critical paths, earned value, honest risk registers, and governance that helps rather than hinders.

We also learned something the textbooks only hint at. Much of the effort in running a project goes on administration: chasing updates, reconciling spreadsheets, rebuilding the same report for a different audience.

Capable people were spending their days feeding the tools instead of leading the work.

03 · Back to engineering

Building the tool we had always wanted

So we went back to engineering, this time with a different question. Rather than build another data platform, we set out to build the project tool we had wished for on every engagement.

That became Qumulo PM: schedule, cost, risk and agile delivery in one place, with the system carrying the administrative load and watching the horizon for trouble.

Building it taught us more than we expected. Every design decision came back to the same question: what should a machine do here, and what should a person do?

The answer was always the same. The machine keeps the record, does the arithmetic and raises its hand early. The person judges, decides, persuades and leads.

04 · The realisation

Somewhere along the way, we realised we had been working on the right problem from the wrong end.

Better data helps. Better method helps. Better tools help a great deal. Yet none of them, on its own, has ever delivered a project.

People do. A team that trusts one another, shares a clear picture of the goal and is willing to say early when something is wrong will outperform a better-equipped team that isn’t.

We had seen it on every project we ever ran. It just took building everything else first to see it clearly.

05 · Where we are now

Building good project teams

That is where Sweet Thunder now puts its energy. We help organisations form project teams, shape them and keep them working well together.

Everything from the earlier chapters still matters, and we bring all of it: the data, the method and the tooling. We simply start with the people now, rather than arriving at them last.

People handle judgement and relationships. Tools handle the administrative load. A team, properly built, handles the rest.

06 · Why racing

Where teamwork has nowhere to hide

If you want to see a project team at its sharpest, watch a race team. A race weekend is a project with fixed deadlines, no room for a late status report and every result on public display.

Every role is clear. Every hand-off is rehearsed. Everyone is trusted to do their part without anyone looking over their shoulder. When it works it looks effortless, and it never is.

That is why we created Sweet Thunder Racing: a living example of the teams we help build, and a place where organisations can experience that kind of teamwork for themselves.

---

If this sounds familiar

Good work that doesn’t quite land. Capable people buried in administration. A group that never quite becomes a team. We have been there, more than once.

We would be glad to talk. Not to sell you a method, but to share what we have learned and help you build a team that delivers.