Frameworks Were Made on Someone Else's Boat
In short: frameworks are a great place to start, but they were built for someone else's situation. What makes them work is understanding the principles behind them, the WHY, and then adapting the steps to fit yours. Even the product trio can look different, as long as its principles stay.
Am I a skipper? Not by education.
Everything I know about sailing I learned from experience, from my partner, from books, and from a lot of YouTube videos.
What Did Boats Teach Me About Frameworks?
There are 2 things I learned about boats.
The first is that the theory will only take you so far.
The second is that every boat and every system is similar, but different from any other boat. Each boat has its own story: the way things were installed and the way it was built. A system that was installed on one boat might be installed completely differently on another.
So understanding how things work, the principles, was much more important than learning a specific way of doing things. When you understand the why behind the steps, you can take what someone explained in a video on a similar boat and adapt it to the one in front of you.
And I think this is true for everything in life, and for work too.
Why Don't Frameworks Work as They Are?
Frameworks are great to start with, but they were made on someone else's boat.
They come with assumptions about the organization they were built for: its people, its structure, the way it works. When those assumptions don't match yours, following the steps exactly can make things harder, not easier.
That doesn't mean the framework is wrong. It means you need to know what each part of it is there for, so you can keep what matters and adapt the rest.
What Does This Look Like at Work?
Take the product trio.
In a SaaS company, the trio is usually a product manager, a product designer and a tech lead. But the trio isn't about those three job titles. Its goal is to bring different perspectives into the room, so the team can manage the four product risks together: value, usability, feasibility and viability.
The organizations I work with don't always look like a SaaS company, and their trio doesn't either.
For a service, you might not need a product designer, you might need a service designer. And instead of developers, the support team might be the right people to bring the feasibility perspective.
The titles change. The principles stay: the right perspectives in the room, all four risks covered, a team that owns the problem, and a way of working that isn't just another project.
Principles, not framework.
How Do You Adapt a Framework to Your Organization?
Before you adapt a framework, ask a few simple questions:
1. What is this part for? What problem does it solve, or what risk does it reduce?
2. Do we have that problem too? If you do, keep the principle. If you don’t, you might not need this part at all.
3. What does it look like in our world? Who are the right people, and what are the right steps, for your organization, your customers and your way of working?
4. Did it work? You rarely win on the first attempt. Even if you start from the original structure, build small, run, learn and adapt. Keep yourself agile, just like with any other product. Change the steps, keep the principle.
The steps can change. The WHY is what you want to keep.
FAQ
Should you follow a framework exactly?
Frameworks are great to start with, but they were built for someone else's situation. Learn the principles behind them and adapt the steps to fit yours.
What is the product trio?
In SaaS, it's usually a product manager, a product designer and a tech lead, working together to manage the four product risks: value, usability, feasibility and viability.
Does the product trio have to be a PM, a designer and an engineer?
No. The principle is to bring the right perspectives to cover all four risks. In a service organization, that might mean a service designer instead of a product designer, and the support team instead of developers.
How do you adapt a framework to your organization?
For each part, ask what it's for, whether you have that problem too, and what it should look like in your world. Keep the principle and adapt the steps.
Frameworks are great to start with. Just remember they were made on someone else's boat.


Comments