Bluehook Resource Centre

Before the Resource Centre existed, product education did not live in one designed surface. Useful content existed, but it moved through support conversations, training links, shared folders, manual lists, and videos sent when customers asked for help.

That worked for one-off support moments, but it did not scale well for a product that needed clearer onboarding, stronger go-to-market support, and a more self-serve way for people to learn.

When product knowledge is scattered, users struggle to build momentum. Support teams lose time answering repeat questions. New users depend on someone knowing what to send, when to send it, and where it lives.

For Bluehook, the opportunity was to make learning feel more intentional: a place where people could browse by topic, understand what a video covered, and revisit guidance without needing a support handoff every time.

A user can understand a feature, trust a workflow, or feel ready to try something before they ever open the app. For Bluehook, the Resource Centre became a way to package product knowledge in a format that supported learning, sales conversations, onboarding, and customer enablement.

The real design question became:

We looked at patterns and tooling in the world of Userpilot, UserGuiding, and in-app onboarding. Those tools can be useful, but for this moment they were not the best fit.

They were more operationally demanding, more tightly tied to in-product guidance, and better suited to a later stage of product maturity. Bluehook needed something lighter and faster first: a learning layer that could support go-to-market immediately, live outside the app, and become easier to maintain as the content library grew.

A big part of the work was shaping the information model: video titles, subtitles, categories, tags, groupings, and the logic of how someone would browse.

The Resource Centre needed to feel useful at a glance. That meant creating a structure that could hold different kinds of learning content without becoming another messy folder.

The final direction brought product education into one public-facing destination. Users could browse by category, scan resource cards, open a video in context, and return to the library without needing to ask support where to start.

The Resource Centre created a stronger foundation for product education, support enablement, and go-to-market storytelling.

Sometimes the most useful move is to create the layer around the product that helps people understand it in the first place.

The Resource Centre did not try to solve every onboarding problem. It created a clearer first step: a practical, browsable, maintainable place for product knowledge to live.