batteriesincluded.com · Questions & Answers

How much time should our employees spend with a forward-deployed engineer, and do they need to attend every Level 10 Meeting?

Plan targeted access to employees and decision-makers, not constant meeting attendance. A forward-deployed engineer needs to observe real work and resolve questions quickly, but does not need to join every leadership conversation.

Before the engagement starts, agree on a working rhythm that includes process observation, short decision sessions, and demonstrations using realistic tasks. The time required depends on workflow complexity, so ask for an explicit participation plan rather than accepting an undefined promise to embed.

Give the engineer access to three kinds of input:

- Frontline employees who can demonstrate routine work and exceptions.
- The process owner who can explain policy and approve workflow changes.
- A leadership contact who can resolve priorities and cross-department decisions.

Avoid making employees act as full-time software specification writers. The engineer should observe, document what they learned, and bring back concrete questions or a working example. Lovable and Replit can support rapid iteration, but speed of building does not replace understanding the job.

Keep the Level 10 Meeting focused on its established agenda. Invite the engineer when their input is needed to solve a specific issue, rather than turning the meeting into a development status review. Track a relevant Rock through the existing cadence and put genuine blockers on the Issues List.

My recommendation is to protect scheduled feedback time and maintain a clear decision log between sessions. If employees repeatedly explain the same process or wait on unresolved questions, change the collaboration method. Good embedding reduces translation overhead without taking over the team's calendar.

Category: Forward-Deployed Engineering

← All questions