How we will work together
We agree the work before starting. You review it before publication and know what the handover includes.
Let’s talk about your next stepUnderstand
Define the work
We begin with your work: who your service is for, what a visitor needs to know, or which task you want help with. We also look at the material and tools you already use.
We agree which pages or tasks are included, what you will provide and what we will review together.
Size and space give each question a different weight.
Give it shape
Decide what to connect
For a website, we organise the pages and the route to contact. For AI work, we identify the information and tools the system needs to access.
Access to a source and permission to change it are agreed separately.
Changing a source requires a separate permission.
Build
Review before a change is made
You review a working version of the website before it is published. For an AI system, we define where a person reviews a proposed action and how they can ask for changes or stop it.
We check what happens when information is missing, a connection fails or a request needs correction.
Proposed change
A person reviews what will change
Execute the approved change
Return for review before executing
Do not execute
Review
Prepare the handover
We check navigation, forms and reading on different screens. The handover explains how to update the website and what needs regular review.
We agree who will look after content and external services after publication.
- Write
- Edit
- Publish
- Review
Reviewing a published piece can lead back to writing and editing.
What an approval needs to show
Before approving a change, a person needs to see what will happen, which information it uses and how to correct it. The film follows those points of review.
Read about limits and permissionsRead the visual story
Supervision connects a proposed change with its context and three possible decisions: authorise, revise or stop.
Show the proposed change. Before deciding, a person needs to see what would be modified. A proposal sheet contains the change, affected items and missing information. There is no connection to execution yet.
Provide the context. Information sources and open questions travel with the proposal. Source and Questions connect to the proposal. Review receives both the change and its context, not just an approval request.
Approval and revision are different decisions. Revision returns the proposal to editing before another review. Review opens two paths: Authorise leads to the action and Revise returns to the proposal.
Missing information can stop the process. A required missing fact keeps the action pending. A missing fact connects to Stop. The action path is interrupted and the missing information is identified.
Keep the decision and its scope. The record makes the authorisation and its context reviewable. The decision connects to a record of Change, Permission and Context. The record remains linked to the review that produced it.
This video could not load. You can read its complete visual story above.
Let’s work out the first step
Use the contact form to tell me what you need and what you already have.
Arturo OrdóñezNicaragua