Vendor access
This part is for Aigna staff
Vendors see their own installation and the device reference they need to build it: device types, setup guides and models. Everything else stays with Aigna.
Go to your installationKeia Method· Level 2 · 2.5 · idea 5 of 5
Learn as you go
Put what people need to know where the work is, and keep what they learn where the next person will look.
Learn as you go
- Instead of
- courses apart from the work, and fixes that live in one person's head.
- You
- keep each setup guide beside its device, and write down what fixed a fault where the next person will look.
- You'll know it's working when
- a repeat fault is fixed from last time's note, and a new starter sets up a room right first time.
In Keia Atlas: the setup guide opens beside the device, and a job shows what fixed it the last two times.
In the morning story, this is 08:31: The network team turns the port on. Liam checks the room and closes the job with one sentence: what fixed it. The sentence is kept in the record, against the video bar. Read the story
In full, with no software
- Instead of
- Training apart from the work, and knowledge that leaves with people. 42% of role knowledge is unique to one person (Panopto). Knowledge management is the weakest service management practice: 20% say it works (Axelos, 2022).
- You
- Put the knowledge where the work is. The setup guide sits beside the device being configured; the incident shows what was tried and what fixed it the last two times; each lesson ends with a thing to try. Guidance is full the first time and shortens as a person's own record shows they no longer need it. Rarely used procedures come back in full after a long gap.
- The moves
- Place the guide beside the device, the fix on the record where it was found
- Capture what you learnt goes on the record, with your name
- Shorten steps a person no longer needs fold away, and come back after a long gap
- Progress, never points
- Show team progress on real outcomes (spaces that worked first time this month, problems fixed for good), and impact on the record ("Boardroom back for the 10:00"). A personal mastery record is private and opt-in and only shortens checklists. No leaderboards, no per-person rankings, no streaks, no points for volume or speed.
- You'll know it's working when
- First-timers set spaces up right first time; new starters become competent sooner; captured fixes are reused ("used on 14 installs"). Measure all three.
In Keia Atlas
The same guide, shorter each time
Setup guide · Studio X in Google Meet mode · 7 of 14 steps shown
- Pre-flight
Confirm the model is supported and a Google Meet licence is free. The port gives DHCP and NTP and reaches zto.poly.com, lens.poly.com and swupdate.lens.poly.com on 443. Stage on a port without 802.1X. In Poly Lens, set the site policy to no automatic updates before the device arrives.
- Connect HDMI, Ethernet, then power
Note the IP address shown on screen. The default login is admin with the last six characters of the serial number.
Why this order: The first boot goes straight to Poly's zero touch service. On a port without the right access it stalls or picks the wrong mode.
- Complete the setup prompts
The device contacts Poly's zero touch service to choose its mode. Do not pick a provider yet.
- Log in and set the admin password
Use the site's password from the vault. Do this before pairing the TC10.
Why this order: From 4.6.0 setup forces a new password, and every later step needs the admin login.
- Turn off automatic updates
Clear Enable Automatic Updates, and check Only Check for Updates During Maintenance Hours is not quietly on. Do this before choosing Google Meet and before Poly Lens.
Why this order: Device Management is behind the admin login.
- Country, time zone and time server
The default zone is US Central. Dublin and London share one zone value.
- Device name, room name and contact
The hostname, the room number and name, and the site's AV team as contact.
Every step with its detail and why the order matters.
The setup guide opens beside the device. The Help switch explains any control on the screen you are on. Every lesson has a task to try in the demo. A captured fix becomes a proposal to the setup guide, approved by its owner.
Why it works, and its limits
- Why it works
- Training transfers only where it is applied at once; step-by-step help that aids a novice hurts an expert; visible progress on meaningful work is the strongest motivator measured; points and leaderboards at work crowd it out.
- Limits
- People must keep doing the diagnosis. On a P1 or P2 the person records what they think before a suggestion is shown; any rule can be run by hand to keep the skill.
What it maps to
| On screen | Plain meaning | Maps to |
|---|---|---|
| Knowledge, Runbook, Lesson, Proposal | Know-how; steps; what was learnt; a proposed edit to a standard | ITIL knowledge management |
| Setup guide, Build sheet | The settings for a model, in order; every setting's actual value for one unit | Configuration |
| Problem, Known error | The cause behind repeating incidents; a cause with a known workaround | ITIL problem, known error |
Try it in the demo
Opens as Anna, a delivery engineer. Everyone in the demo is made up; nothing you do leaves this browser.
- Open the setup guide for the video bar: the settings in order, beside the device.
- Press ? to switch Help on, then point at three things on the page.