What is product activation?
Product activation is the moment a new user first experiences the core value of a product — not when they sign up, but when the product does the thing they came for. Work on activation is work on the path between those two moments: the steps, screens and decisions a user passes through before the product has proven itself. Acquisition brings people in. Activation decides whether they stay.
Why do users sign up and never come back?
Users who leave after one session almost never reached the product's core value. The usual causes are a setup flow that asks for a lot before it gives anything back, a first screen with no obvious next step, and a gap between what the marketing promised and what the first session delivers. The fix is rarely more features. It is a shorter, clearer path to the first useful outcome.
Why do users fail to experience a product's core value?
Users don't always fail because a product is difficult to use. Often they fail because they never reach the moment when its value becomes clear. They sign up, explore a few features and interact with the product, but never complete the actions that lead to a meaningful outcome. The path from initial interest to experienced value is broken, unclear, or simply too demanding. This is an activation problem, not a usability problem — a product can be intuitive and well designed and still fail to help users achieve their first meaningful win.
What is time-to-value in SaaS, and how do you reduce it?
Time-to-value in SaaS is the time between a user signing up — or starting to use the product — and reaching their first meaningful outcome. It matters because users who experience value quickly are more likely to stay and expand, while a slow time-to-value usually means people sign up, drift, and quietly leave. You reduce it two ways: remove the steps that do not contribute to that first outcome, and move the outcome itself earlier — sensible defaults instead of configuration, sample data instead of an empty state.
How do you find where users are dropping off?
You map the journey as it actually exists, then measure every step of it. That means defining the path from entry to first value, instrumenting each step as an event, and reading where the step-to-step completion rate falls rather than where the overall funnel number sits. Event data shows where users leave; session recordings and support tickets explain why. In most products, one or two steps account for the majority of the loss.
How do you simplify a product without removing essential functionality?
By recognising that simplification and removal are different operations. Simplifying a product does not mean removing features indiscriminately; it means making the path to its core value easier to understand and act on. The distinction that matters is between what the product needs to do and what a user needs to see or do right now.
One caution. When users say a product is too complicated, they are usually describing something else. Either they cannot tell what the product is for, which is a positioning problem, or they cannot find what they already know exists, which is information architecture. Cutting features resolves neither, and burns capability you will want back.
How long does it take to fix a product's activation problem?
About two weeks, when the scope is one path rather than the whole product. The Think in Systems Product Activation sprint runs two weeks: map the current user journey, identify where users drop off, and rebuild the most important path. Rebuilding an entire product takes considerably longer, but the first measurable improvement almost always comes from one flow — which is why the flow comes first and the redesign comes after.
What is a Product Intelligence Layer?
A Product Intelligence Layer™ is a single shared system holding the context a team needs to make product decisions: the activation strategy (what value means for each user type), the design system and design standards, product goals and metrics, and competitive context. Think in Systems builds it so that context lives in one place rather than in people's heads, stale Figma files and unread decks — and so that AI tools and new hires work from the same source.
Can AI replace a product designer?
AI produces screens quickly, but it cannot decide what the product should do, for whom, or why — and without that context it produces work that looks finished and solves nothing. What AI does change is leverage. A team whose activation strategy, design standards, metrics and competitive context are written down can get senior-level design output from AI tools. The constraint is not the model. It is whether the context exists in a form the model can use.
Should we hire a product designer, use a freelancer, or work with a studio?
Hire in-house when the product needs continuous design work and you can keep that person busy and supported. Use a freelancer for contained, well-defined deliverables. Work with a studio when the problem is a system — an activation path, a user journey, a design standard — and you need it diagnosed and rebuilt faster than a hire can be found and ramped. Many teams do both: the studio sets the system, the in-house designer runs it.
We haven't launched yet. Is activation work premature?
No — pre-launch is the cheapest time to do it, because there is no existing journey to unpick and no shipped habits to protect. Defining what value means for each user type before launch gives the product a foundation, so every later redesign improves a path that already works instead of patching one that never did. Post-launch activation work starts with diagnosis. Pre-launch work starts with designing the path itself.
How do you know a redesign actually worked?
By setting the target before the work starts, then measuring the same path afterwards. At the outset we agree a target time-to-value — a specific number the rebuilt path has to reach — and that target is what the work is measured against. Supporting measures are activation rate (the share of signups that reach first value) and step-level completion along the rebuilt path, with week-one and week-four retention as the lagging check. A redesign that improves how a product looks without moving those numbers has not been validated, only shipped.