Product management

There's a timeless debate in software development about the difference between project management and product management (and don't even get us started on "program management"). These terms get used interchangeably and usually cover all the work outside design and development that's needed to get projects over the line.

While there are similarities between these disciplines, the differences matter. They're part of what shapes our identity and sets us apart in a sea of generic software houses.

We've already covered Project management in detail, but in short, we see it as the timeline management and client communication needed to build and release a project. It's about coordination: building roadmaps, managing tickets in Notion, and keeping clients informed about progress and potential pitfalls.

We're good at project management. Better than most. But honestly, this type of work isn't all that different from what clients would get with most outsourced development agencies. And while it helps ship products, it doesn't guarantee you're building the right product for your users.

That's where product management comes in, and it's where we really separate ourselves. Instead of just coding what clients tell us to build, we partner with them throughout the entire process. Their success is our success, so we're invested in making sure their products and businesses actually work.

We bring ten years of accumulated product insights to the table, embedded in deep conversations at every stage. Our Product Discovery process starts before we draw a single wireframe or write a line of code, and we continue to support our clients with user testing throughout the project to ensure they're on the right path.

Our approach

We break our product development down into three project types: brand new builds from scratch, redesigns that improve usability and conversion, or expansions that add new functionality to existing projects.

We also offer five core processes: Project Kickoff Meetings, Product Discovery Workshops, Information Architecture, Branding Workshops, and User Testing. Depending on the project type, some are required, others are optional and delivered based on client needs.

That said, these are frameworks, not rules. We adapt our workflows to each client's unique situation.

Data and intuition in balance

Our approach to product development blends data analysis with intuition. Sometimes we need to dig deep into the numbers before finding the path forward. Other times, our experience is enough to guide the next iteration. We take whichever approach makes the most sense for the situation at hand.

All of this only works when we're partnering with clients who value product insights and are open to implementing them. Read more about the kinds of clients we work best with in the Culture section.

Dive deeper into our product management processes and best practices in this section to see how we guide clients toward building better products.