QUESTIONS / GUIDANCE / NEXT STEPS
Tutorials
Rehearse a website change before publishing it.
Choose one representative page and record its starting state. Make the intended change on a controlled copy, then review headings, links, images and the editing experience using actual content.
ORIGINAL EXPLANATORY CONCEPT / NO CLIENT RESULTS
EDITORIAL STUDY / WORKING DRAFT
Tutorials
Context
Experience
Ownership
Tutorials — the relationships to plan.
01 / THE IMPORTANT CONNECTIONS
Start with the decisions that shape the experience.
Use context, experience and ownership as a starting point for a focused discussion.
01
Context
Start with one decision or task rather than an entire technology landscape. Establish what a useful answer would change.
02
Experience
Identify the platform, users and constraints involved. Distinguish general guidance from advice that requires access to the actual website.
03
Ownership
A tutorial should state its starting assumptions, expected result and recovery point. Use a representative example and distinguish a demonstration from instructions suitable for every production site.
THE APPROACH / FOUR USEFUL STAGES
A process built around a useful decision.
01
Choose the question to answer
Start with one decision or task rather than an entire technology landscape. Establish what a useful answer would change.
02
Gather the relevant context
Identify the platform, users and constraints involved. Distinguish general guidance from advice that requires access to the actual website.
03
Work through a practical example
Use a representative scenario or checklist. Label concepts and demonstrations clearly instead of presenting them as client outcomes.
04
Choose the next action
Document the decision and unresolved questions. Use the related services or project enquiry route when a scoped review would help.
A LITTLE CLARITY BEFORE THE NEXT STEP
Questions worth asking.
What should I bring to a tutorials discussion?
Choose one representative page and record its starting state. Make the intended change on a controlled copy, then review headings, links, images and the editing experience using actual content. Bring the existing website or a representative example, explain the customer task and identify the constraints or decisions that are still open.
How do we review context?
Use a representative scenario and agree what a useful outcome would look like before changing the wider experience. For Tutorials, the discussion should connect context with experience and the people who will maintain the result.
What happens after the initial discussion?
The next step is to agree whether a scoped review or project is appropriate. Deliverables, access, dependencies, costs and timing need to be confirmed for that engagement. A conceptual illustration on this page does not represent a completed client project or promise a result.
YOUR NEXT CHAPTER
Make the next decision about tutorials a clearer one.
Tell us what you want to improve, the content and systems involved, and what a useful next step would look like. We can use that context to discuss a suitable scope.