Software projects get better in two ways: from measurements, and from people telling you the truth. We rely heavily on the second one.
Feedback Starts in Discovery
The most valuable feedback we get isn’t about our work. It’s about the client’s process. In the first days of a project, we’re usually learning that the way work actually happens differs from how it’s documented. Clients tell us what’s really going on: the spreadsheet that runs the business, the one person who knows how the system works, the approval that only happens in email.
That’s feedback too, and it changes the shape of everything we build.
Feedback During the Build
We show working software every week and ask the uncomfortable question: is this actually useful, or are we just executing? Clients who say “that’s not how we’d use it” during the build save us from building the wrong thing for weeks. We’d rather hear it early than discover it in the launch retrospective.
Feedback After Launch
The truth arrives after go-live: adoption numbers, support tickets, the things people stop doing now that the software handles them. We track these because they’re the real measure of whether the project worked. The most useful feedback is the kind that tells us what to improve in the next phase, and most of our client relationships are multi-phase for exactly that reason.
If you have feedback about how software projects should be run, we’d love to hear it. Get in touch.