Benjamin Johnson
Back to the workbench

Step into the work.
Bring Bob with you.

“Bob, look at this with me. Now let’s see what we could build.”

Start in the room around you. Expand into a virtual studio. Talk through an idea, shape a product or walk through the systems behind a service—with the same collaborator beside you.

Current stage: illustrated concepts + interactive browser mock-ups
Illustrated EMBODY concept: grey-haired Ben wearing Vision Pro shares a workbench view with human-avatar Bob, then both explore a larger virtual architecture model with service and security signals.
MR / bring the work into your roomVR / make the world your workspace

AI-generated concept illustration · the intended experience, not a photograph or recording of a working XR system.

THE QUESTION

What if the conversation
had somewhere to happen?

I want to point at a sketch and ask Bob a question without reconstructing it in a prompt. Then spread an idea across the room: customer outcomes, architecture, service design, an agent team and the awkward dependencies. When something breaks, I want to explore the service—not shuffle between disconnected dashboards.

Build it with Bob beside you.

The offering sits in front of you. Its service, platform and team layers unfold in space. Point to a component, ask Bob a question and compare a proposed design branch while keeping the original in view.

First-person immersive VR studio: Bob stands beside the viewer, pointing into a floating AI-assisted service desk architecture. The viewer’s hands compare local-data and managed-cloud branches beneath service, platform and team layers.
AI-generated first-person VR concept · illustrative architecture and interface, not a running headset application.View full size

The amber component is a proposed alternative. The conversation, selection and comparison stay together; the design can be explored before any change is made.

See together. Think together.
Build something useful.

Three connected interface studies. Try the shared view, carry a service into the operations space, or switch into the VR design studio and shape a brief of your own.

EMBODY / EXPERIENCE LABInteractive mock-up · synthetic data · no connected systems

Bob, look at this with me.

Stay in your room. Share a selected view, point to something and give the conversation a common reference.

ONE CONVERSATIONBob + youBrief and selection stay in this walkthrough when you change modes.
ROOM + SELECTED CONTEXTExample view private
Your room stays visible.
The work comes into focus.
SELECTED VIEW / Bench model

Only you can see this example view.

Choose what Bob seesThis controls the mock-up only. No camera or microphone is accessed.
Speak · point · select · expand · compare · create

Here, buttons stand in for a spoken exchange and spatial input. Live voice, vision, headset interaction and operational data are not connected in this mock-up.

Interactive concept · every system, incident and conversation here is synthetic or scripted. No camera, microphone, live Bob connection or operational integration is active.

Mixed reality / shared attention

“Can you see the bit I mean?”

Talk to Bob while sharing a selected sketch, application view or permitted scene context. Keep the sharing state visible and stop it when the task is done.

Virtual reality / creation

“Let’s build the offering around that.”

Move between a whiteboard, product model, architecture, operating model and team design. Compare branches and leave with an inspectable brief, not just a memorable meeting.

Operations / understanding

“Show me who this issue affects.”

Connect services, VMs, workloads and network paths with ITSM records, SOC signals and observation times. Follow the evidence, compare a change and rehearse a response.

Same Bob. Another way to be there.

A small desk robot could give Bob a way to turn, listen and share attention. A separate portable edge computer could later support local processing and device connections.

Revised hardware concept: a small desk robot, a separate fan-cooled edge-compute board and an upright white UniFi Travel Router with a portrait display. Separate Vision Pro and three-pill-camera Quest 3 sketches sit behind them.
AI-generated hardware concept using supplied device-appearance references · illustrative robot and edge board; not an assembly plan or a built system.

Start with presence.
Earn the portable kit.

The first experiment can use an existing computer and a simulator. Dedicated edge hardware comes later, if measured workloads justify it.

The current portable-compute candidate is an NVIDIA Jetson Orin Nano Super. A Reachy Mini-style endpoint and UniFi Travel Router are part of the proposed physical direction. Exact hardware, power, cooling and network behaviour still need validation.

POSSIBLE CONNECTIONS / NOT A LIVE NETWORK
Robot endpointAttention, speech & local stop
Edge hostExisting host first · Jetson candidate later
Spatial interfaceVision Pro direction · bounded Quest comparison
UniFi Travel RouterProposed local network + controlled uplink

Encrypted, authenticated connection
To be configured and tested

Bob’s core servicesIdentity, authoritative memory & policy stay here
What “secure access” needs to mean here

The router is a network component, not a guarantee. The design calls for authenticated outbound connectivity, restricted local control and a visible safe state when the connection fails. The selected hardware and configuration must demonstrate those behaviours before I describe the setup as secure or dependable.

Public device references: NVIDIA Jetson and UniFi Travel Router. These inform the concept; they do not establish an integrated EMBODY system or vendor endorsement.

Make one real task
better than a chat window.

The ambition is broad. The next proof should be specific: a spoken exchange with Bob, a correctly shared reference, a transition into the spatial model and an outcome we can inspect afterwards.

This browser mock-up demonstrates interface behaviour. The working experience is still to be built and tested.

  1. Talk and share attention

    On a headset, ask Bob about a deliberately selected synthetic object. Check that he receives the correct context and stops receiving it when sharing is off.

  2. Carry the work between MR and VR

    Keep the same selected object, brief and conversation while changing the view. Test comfort, clarity and the time needed to complete a useful task.

  3. Create and investigate

    Finish with a reviewable design brief or a diagnosis supported by linked observations. Compare it with doing the same task on a normal screen.

How shared vision would work on the actual headsets

The intended experience needs an explicit shared context: a selected model, app view, image or permitted camera input. Seeing passthrough in a headset does not automatically give an application that camera feed. Apple’s main-camera API has enterprise access requirements; Meta’s passthrough camera API requires the appropriate device permissions. The native prototype must validate the allowed route on each target device.

Would you try a shared workspace or a little robot first?

I’m interested in where it would help—and where it would just get in your way.

Tell me what you think
Meet Bob Back to the current snapshot Design snapshot · 8 November 2026

The story behind this experiment

From racks to agents.

The rack in the workshop is part of the story. This essay follows the machines, the work and the curiosity that brought me here.

Keep up with Ben + Bob

Follow the build. Awkward bits included.

The next proof is a real task: what we tried, what broke and whether sharing the workspace helped. Follow the experiments; the fuller notes will stay here at VirtuallyNoIdea.

Check the current build notes on Now