Training Session

Products often go unused after the contract is signed, because the person who decided and the people who will use it are not the same people. Whoever signed knows what was bought; whoever opens the screen next month is seeing the product for the first time.

Sending documentation doesn't fill that gap. Searchable docs only help someone who knows what to search for, and a first-week user doesn't yet know what they don't know.

Pagedeck had exactly this happen. A customer Sofia signed logged in four times over two months and created zero documents. On a call, the contact said they'd been putting it off because they didn't know where to start. The help center link had been in the contract email and nobody opened it. This is why the most expensive format in customer education has survived: the person running it finds out what the customer doesn't know and changes the content while they're in the room.

Five steps.

1. Listen before you open it. A 30-minute pre-call establishes what work the customer intends the product for and who will attend. Skip this and the prepared examples float free of the customer's actual job, and the session fills with people asking how this applies to what they do.
2. Rebuild the examples around that customer's work. Meeting notes for a customer who wants meeting notes, a draft agreement for a customer doing contract review. Using the sample documents that ship with the product puts understanding one step further away.
3. Split the hour into four. Ten minutes confirming what this customer is trying to achieve, 25 minutes of the manager demonstrating on screen, 20 minutes of attendees doing it themselves, five minutes of questions. Drop the third block and almost nothing survives the session. Watching and doing are different activities, and the places people get stuck only surface when they click for themselves. Those stuck points are also the most useful thing the session produces, because they are the same points every other customer will hit.
4. Leave something behind. The recording, a summary of what was covered, and three things attendees will do next week. Questions from the session that other customers will also ask move into a help document; hearing the same question a third time is the signal to write one.
5. Check back in two weeks. Open the usage signals — login frequency, whether core features get touched — and see whether those three things actually happened. If they didn't, suspect the sequence or the attendee list before suspecting the content.

Who is in the room decides the outcome more than anything else. More than half the attendees have to be people who will personally open the screen. A session attended only by decision-makers feels good and shows zero usage two months later. Too many people makes hands-on practice impossible, so keep a single session under about twelve.

Split by role when roles are mixed. An admin session about permissions and configuration and a user session about creating and sharing documents barely overlap. Put both in one hour and everybody sits through thirty minutes that has nothing to do with them.

There are four timings. The first is within two weeks of signing, scheduled after the onboarding specialist has finished the initial configuration, since the account has to be set up. The second is right after a significant feature ships — written release communication covers most cases, but a feature that changes how people already work goes faster sitting together. The third is when the customer's own contact changes, because the knowledge in that account resets to zero when the person who had it leaves. The fourth is three months before renewal, and only when significant capability is going unused.

There are also times not to hold one: the account isn't configured yet, the attendee list isn't settled, or the customer urgently needs one specific problem solved. In that last case, solving the problem directly beats teaching, and the session moves to a week later when there is room to learn rather than to firefight.

Costing it out makes the decision easier. Two hours of preparation plus one hour live means a single manager can't run much past ten a week. So the targets narrow to the largest accounts and the ones whose early adoption is wobbling. For everyone else the same content has to arrive in a form that costs nothing per customer, which is what documentation and in-product guidance are for.

"Book the 30-minute pre-call before this session. Walking in without knowing their workflow means the examples float."

Running it without that prep wastes the preparation.

"Don't put admins and end users in the same session. Both sides waste half of it."

Blocking a mixed attendee list.

"We ran the session and usage is flat two weeks on. That was a demo-only run with no hands-on block."

Naming what a session missing its practice block produces.

Pagedeck reserves this format for enterprise customers. Teams that started free get in-product guidance and documentation; customers on annual contracts get an hour booked within two weeks of signing. Last quarter, the 22 accounts where that rule held created more than three times as many documents in their first month as accounts that started without a session.

There was a failed run in the same quarter. Fourteen of eighteen attendees were in the approval chain and the team that would actually use the product wasn't there. Sofia reopened a practitioner session two weeks later, and now confirms the attendee list with roles written out during the pre-call.

The most common reading is that one session completes adoption. People nod for an hour and ask questions, so it feels finished. But what was learned disappears unless it gets used the following week. A session with no follow-up and no three named actions is indistinguishable, in two-month usage data, from having done nothing. Left uncorrected, the team reports session counts as results while adoption sits where it was, and the number that goes up in the quarterly review is the one nobody outside the team cares about.

Believing more features shown is better is the second mistake. An hour was granted and it feels wasteful not to fill it. In practice, covering more than three things in a first session means attendees remember none of them. Creating a document, sharing it, and getting review through comments — those three, with links for the rest — reads better in next week's usage than a full tour.