Certification

Early in a contract, someone from the vendor teaches directly. That's a training session: a scheduled call where a rep walks through the screens and takes questions on the spot. With ten customers this works better than anything else, because you can hear what a company plans to use the product for and build the examples out of that work.

At a hundred customers the same approach breaks. The load is only half of it. The harder part is that what gets taught doesn't stay inside the customer's organization. A session ends and is gone, and if the person who attended moves to another team six months later, that company has nobody left who knows the product. This is how a 300-seat account ends up sending "how do I change admin permissions?" for half a year under a different name each time.

Piling up help documents solves half the problem. Search-and-read works without anyone present, but if nobody knows what to search for, the search never happens. Certification changes the direction: instead of pushing knowledge out, it creates people who hold it. Two certified administrators inside an account means most of that company's questions end before they reach the vendor.

It starts by writing down, in sentences, what someone has to be able to do to pass. From there the sequence is roughly five steps.

1. Define the scope — write it as behavior, as in "can design a permission structure and configure external sharing policy." A line like "understands the product" never turns into an exam question and has to be caught here.
2. Build the material — attach a video or a hands-on document to each item in the scope. Existing help documents become the raw material, with the administrator-facing ones pulled out and resequenced.
3. Design the exam — write the questions and set the passing mark, something like 70 points out of 40 questions. Mix in tasks that have to be performed on screen rather than only questions that reward memorization.
4. Sit and score — run it online with automatic scoring. People who fail usually get a retake after two weeks along with a breakdown of which areas they missed.
5. Issue and renew — hand the certificate and badge to those who pass, with an expiry attached. One or two years is common.

That expiry in the last step is the piece most often skipped. If the product changes substantially every six months and the credential never lapses, someone certified three years ago is running internal training against menus that no longer exist. Attaching a term forces relearning at each renewal, but it also means the material has to move in step with release communication — the notices that tell customers about new features and changed behavior. Every notice that goes out brings a check of which chapter just went stale.

Three groups take it: administrators who run the product inside a customer, consultants at partner firms who install and configure it on a customer's behalf, and the vendor's own sales and customer success staff. Their reasons differ. The first group certifies to answer questions inside their own company, the second to sell, the third to be qualified to explain.

Timing is set by the state of the product. Don't build one while the screens turn over every quarter. Material and questions take two or three months to produce, and half of it will be out of date by the time it's finished. The right moment comes when the core screens have held still for about a year and the customer count has passed a few dozen, so the same question starts arriving from several companies at once.

What each customer pays matters too. A product with thousands of customers paying a few tens of dollars a month has no room to staff certification, so documents and a knowledge base — one place where those documents are gathered, categorized, and searchable — come first. A product with fifty customers paying $75,000 a year can staff certification and still come out ahead.

"The goal this quarter is getting 20 partner consultants through certification."

Growing the number of people outside the company who can deploy the product.

"That account has a certified admin, so we barely hear from them."

A high share of questions gets resolved internally, which keeps support load low.

"The product moved this much and the courseware is last year's. Let's refresh it first."

A warning that everyone who passed is working from screens that no longer exist.

At Pagedeck, Sofia heard the same thing three times while negotiating enterprise renewals. The contract would hold, but expanding to more departments was hard because nobody internally really knew the product. Adding seats meant someone in the new department had to own the configuration, and nobody volunteered.

Instead of running another session, Sofia proposed building an administrator certification. What changed for the customer was that their admin stopped saying "I know a bit about this" and started holding a credential the vendor stands behind. Once that admin began running internal training, the conversation about expanding seats restarted.

It's easy to expect that certified people will use the product well. They passed an exam, so it looks that way. But an exam measures the ability to pick answers within a fixed scope, not the ability to design a configuration around your own company's work. Attach the program and walk away, and adoption stays flat at accounts with several certified people. Making sure the credential turns into an actual role inside that company is part of the same job.

Assuming it runs itself once built is just as common. Scoring is automatic, so the operating load looks like zero. In practice this is the most expensive of the four formats to create and to keep. Every product change pulls the material, the questions, and the passing bar along with it, and two missed refreshes are enough for the courseware to drift from the live screens. At that point the program stops helping and becomes a channel that certifies and spreads the wrong instructions.