What to understand
The lesson should leave the learner with these operating distinctions.
Explain the difference between the marketing surface and the academy.
Show how the home workspace, login, signup, and password recovery surfaces fit together operationally.
Show where role-based learning paths live and how users should navigate them.
Set the expectation that each surface answers a different operational question.
Lesson walkthrough
The sequence connects positioning, practice, and release upkeep.
Step 1
Surface map
The website explains value, modules, and platform positioning. The academy turns product knowledge into role-based training and completion paths.
Users should not start with random module pages. They should begin with the surface that matches the decision they are making: evaluation, execution, enablement, or release readiness.
Evidence should come from the visible navigation surface, academy path, changelog, login flow, or dashboard signal being discussed. For Surface map, a strong answer names the visible cue, record, status, or reference that supports the next step and states what would pause the learner.
Step 2
Where the source of truth lives
Marketing pages and academy tracks are kept in this repository so the public learning surface stays deterministic. That means stakeholders can trust what they see during rollout planning and discovery.
When a question touches daily workflow behavior, guide the learner to the relevant academy track rather than asking them to infer from marketing copy alone.
For Where the source of truth lives, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.
Step 3
Access journey before live work
Users should understand the difference between the authenticated control center home page and the unauthenticated login, signup, forgot-password, and reset-password pages. Those surfaces decide whether the user is entering the right tenant with the right identity state before any module workflow begins.
Signup, admin signup, and signup review should be treated as controlled onboarding stages. They are not shortcuts around role review or tenant approval.
Use this section to confirm the learner understands more than the page label. They should connect Access journey before live work to the business state, owner, and consequence behind it.
Step 4
Enablement habit to establish early
Teach every new stakeholder to move from module overview to academy track and then to release context. That pattern prevents teams from learning features without understanding operational consequences or rollout sequencing.
Use the section on Enablement habit to establish early as the decision frame. The learner should explain when it matters, who owns the decision, what state they would inspect first, and how that state supports the lesson objective: explain the difference between the marketing surface and the academy.
Use this section to confirm the learner understands more than the page label. They should connect Enablement habit to establish early to the business state, owner, and consequence behind it.
Step 5
Guided practice
Run the lesson as a rollout orientation exercise. Start with the practical task: explain the difference between the marketing surface and the academy. Ask the learner to name the role, surface, evidence, and state they would inspect before taking action.
Evidence should come from the visible navigation surface, academy path, changelog, login flow, or dashboard signal being discussed. The practice should end with the learner connecting the action back to the lesson summary: orient new stakeholders to the website, academy, login and signup journey, and role-based learning paths before you ask them to execute any workflow.
Close the exercise by asking the learner to restate the objective in operational terms: explain the difference between the marketing surface and the academy. They should name what changed, what remains uncertain, and which surface or owner takes the next step.
Step 6
Mistakes to avoid
Do not let new stakeholders treat every page as the same kind of information. Marketing, academy, dashboard, changelog, and workspace surfaces answer different questions. In this lesson, watch for that risk while learners work on this objective: explain the difference between the marketing surface and the academy.
Do not mark the lesson complete because the learner can repeat terms. Completion means they can identify which surface answers a product-value question versus an execution question and describe why the lesson matters in real work.
Review the answer for skipped ownership, missing evidence, or vague next steps. If the learner cannot identify which surface answers a product-value question versus an execution question, keep the lesson in practice mode before marking it complete.
Check your grasp
These statements prove the lesson can be applied without guessing.
Identify which surface answers a product-value question versus an execution question
Point to the academy and changelog without assistance
Explain why consistent academy content matters for enablement
Run a short practice walkthrough around this objective without skipping owner, evidence, current state, or next action: explain the difference between the marketing surface and the academy
Choose the correct knowledge surface for an evaluation, execution, enablement, or release-readiness question in the specific context of this objective: explain the difference between the marketing surface and the academy