Outfindo customer story

Product company 🚀

11-50 ppl 🎩

E-commerce Software 👻

Switched from Asana, Miro 😎

How e-com startup tests assumptions and spots product opportunities

I started using Fibery for product management. Over time, other teams build their spaces there too. Right now, Fibery is our only work-management tool. We also use it as a knowledge base.

How do you set and track OKRs?

We do use OKRs in some form. But given our size and situation, most of the time, agility wins over planning and communication wins over documentation. We all know the business goals we have at the moment and the key metrics and we do all we can to achieve them. We iterate A LOT.

Once we grow and stabilize our business a bit, I can see how Fibery could capture OKRs beautifully. This is what I love about Fibery. It grows with you. As you learn new things, as you expand, as you change your workflow — Fibery is there, ready to fit your needs.

How do you prioritize features?

I do have a very simple scoring system based on impact and confidence. However, it is more of a thinking tool for me rather than a strict sorting system.

I can see the score on cards in views where I want them. And switch them off in other places. And I could sort cards by the score if I wanted to — which I don’t, but I know I can and I love that.

I try to increase our confidence in high-impact activities by testing assumptions and running experiments and MVPs. Very often, we learn by doing — because building something small is cheaper and faster than solid upfront validation.

So, for each major feature, I make a list of assumptions that must be true for the feature to succeed. And I rate our confidence in these assumptions and their importance. And those that are important and have low confidence are those that we need to validate the most. So we gather data to increase the confidence: sometimes market data, sometimes our product analytics, sometimes user interviews — whatever gives the best answer.

All credit goes to Teresa Torres of course, I just try to follow her method and use Fibery to fit it.

And here is story mapping on a whiteboard. I map the flow and create stories for key points right from the whiteboard, this is actually where Fibery shines at its best:

How do you track features and analyse progress?

An NNL (Now-Next-Later) roadmap is the heart of everything. Features have stories and stories sometimes have tasks (used by developers).

I map features to opportunities and have an opportunity tree as a whiteboard in Fibery. Here is a part of it:

Here is also an overview of product areas we spend most of our time on (we don't do story points, so this is based on story count):

How do you do user research?

Even with our limited resources, we invest into continuous research and run regular sessions with potential customers.

Fibery is great for this. Notes and videos from all sessions are there and we have a board of insights that are linked to these notes.

I also set up several fields for data we collect from all sessions (like product price range, important parameters, etc.). And although the interviews are a qualitative tool, as they accumulate, a nice quantity of data gets built up.

Here is a screen of user stats we build from continuous research: