Great software requires great feedback
Feedback drives us to create the right software for our clients — that feedback comes from stakeholders, subject matter experts, users and the code itself.
Without meaningful, structured collaboration and feedback, projects quickly run amuck. Software developers don't think like stakeholders or users and shouldn't work in isolation. When software developed in isolation ships, the poor user experience becomes painfully obvious to the people forced to use the software daily. All because their voices weren’t heard in the development process.
However, misplaced feedback — input from the wrong source at the wrong time — can be a distraction, even a disservice to the development process. That’s why we craft our feedback-gathering process just as carefully as the software we develop. We know when we need an end-user’s input instead of an expert’s. We know when we need to talk with a developer and when we need to talk to an executive. And we’re always listening to the feedback our code is sending to us.
It’s worth pausing here. Because if you’re not familiar with test-driven development, the idea that code can give feedback might seem foreign. But this practice demonstrates an advantage of our craftsman-driven approach. While many software companies run periodic tests to diagnose bugs, we bake tests into the software. Why? Because we know how much time and money can be wasted tracking down the bugs that have crawled in as features are added. Better to craft a system that tests itself, like an intruder alarm for bugs. So we’re confident in our code instead of fearful of what problems we might be missing.
Our Proven Approach: Guiding your software journey
We believe so strongly that great feedback leads to great software that we've structured how we interact with our clients around it: We call it "Our proven approach." We use it again and again — often multiple times on a single project. From new projects to new features, no matter your pace of innovation, our proven approach of using feedback loops to build, measure, and refine works.
We plan flexible project roadmaps quickly. Experience has taught us that, for most projects, hours or days is the right amount of time to develop an initial approach. More initial planning often introduces unnecessary complexity and inflexibility. Less invites chaos. We want to chart a course that allows us to adapt.
As we plan, we identify riskiest assumptions before they can burn through your time and money. We explore quick solutions to close knowledge gaps and identify and execute simple tests. Over the course of days or weeks, we use tight feedback loops with proven validation techniques. We may build prototypes, proof of concepts, test feasibility approaches and more — all in an effort to assure the success of your software project.
Then, we craft. This may last weeks — it might last months. But regardless of the size of the project, we always aim to produce value in small increments. Our clients love this approach: They see their software project come to life one piece at a time. Each bite-sized chunk initiates a feedback loop: A collaboration between developers and the right non-developers. Depending on the situation, we might seek feedback from users, executives, or subject matter experts. And we always make sure that two sets of eyes are on all production code.
As the software gains users, focus often shifts from crafting new features to sustaining the excellent user experience by monitoring the system and responding to user and system feedback. Sometimes this means making small changes — adjustments. But as time goes on, users or potential new users may tell us major features are needed. So, while we continue to sustain the system, we may begin our proven approach for the next big feature or set of features.
Whether we are in a state of constant planning of new features or expecting significant gaps between new features, our proven approach to building and sustaining your software system works. Let's discuss your project