- Industry
- Oil & Gas
- Department
- Design
- Team
- Product Experience
- Kind
- Assistant
- Approver
- Head of Digital Experience
- Code
- DSN-03
It builds a clickable prototype of the screens named, wires the hotspots for each test task and checks every task can reach its success screen. It sets up the usability test with field crews or customers, using made-up asset and production data only, and holds any test with contractors or external participants for approval.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the design workspace: the screens and components to prototype..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Head of Digital Experience with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the user-testing platform: it creates the unmoderated test with the prototype link, tasks and screener, launched or left as a draft. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The testing guide: task writing, screeners for operators and customers, consent forms for employees and contractors, and the rule against testing in live operating areas.
Reads from
the design workspace: the screens and components to prototype.
Acts in
the user-testing platform: it creates the unmoderated test with the prototype link, tasks and screener, launched or left as a draft.
Hands back
An object with prototype_link, tasks (with success screens), screener, consent_needed and launch (true or false).
Asks a person when
The test involves contractors or customers, more than 5 participants, or real data.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Most tasks | 5 | Per session. |
| Session length (minutes) | 20 | Short enough for a break during a shift. |
| Use real operational data | Off | Well names, production figures and customer data are never used. |
| Test in live operating areas | Off | Sessions are held in offices or the training centre, never on live plant. |
| Launch itself up to (participants) | 5 | Larger or external tests need approval. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Use made-up data only when off is off.
- Never plan a session on live plant when off is off.
- Check every task reaches its success screen without dead ends.
- Keep to 5 tasks and 20 minutes.
- Launch only internal tests with 5 or fewer participants; hold the rest.
See the Prototyping Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.