Given what you know at this exact time, what feature (that can be made in a realistic amount of time, with a realistic amount of people) do you bet on to improve your product the most for existing and potential users? So, at the core of Shape Up lies a premise of 'betting': Our solution has been to mold our version of the Basecamp-created framework called Shape Up. In a startup like our own, where there's an endless list of features we want to create, with a relatively small team (we're about 3-4 people working full time with product development), we need to prioritize hard. When we got feature requests and bug reports from customers, it was hard for people outside the product team to understand why we didn't make or fix them immediately. We also saw that it was hard for the rest of the company, the ones working in admin and commercialization, to understand why we did what we did. Were there other more important features than the ones we decided to make? Did we find the wrong solution for this feature? Shape Up our way While developing, we also started questioning our own decisions: not spending enough time digging into the real problems.

We want to hire people who love solving problems and are passionate about building quality products, and not just turning tickets. Several of us in the product team here at ShiftX has been working in consultancies for many years and have met both the positive and negative sides of frameworks like Scrum and Kanban.Īnd while these classic frameworks might work in bigger companies, we wanted a framework that made the product team feel more ownership. The question is old and has many answers. How should you organize your work when you want to build a digital product as fast, painless, and right for the customer as possible?

Shape up basecamp