batteriesincluded.com · Questions & Answers

We already have spreadsheets and a project tool. When should an embedded engineer improve those instead of building us another app?

Start with the tools your team already uses if they can support the desired improvement safely and without excessive workarounds. A new app is not automatically better, and a forward-deployed engineer's job is to solve the business problem, not create more software for its own sake.

Have the engineer watch the workflow and identify the specific friction. For example, employees may be copying the same information between a spreadsheet and a project tool, or waiting for someone to find an item that needs attention. Test whether a clearer process, a better view, or a modest automation in the existing tools addresses that friction.

Before choosing that route, check who can access the information, whether changes can be reviewed, and what happens if the tool or automation fails. Low red tape is useful, but it should not mean bypassing appropriate controls. Also consider whether the existing setup can be maintained by the people responsible for it.

A separate application may be justified if the existing tools cannot support a necessary workflow or access boundary, or if the workarounds create more risk than they remove. Compare both options against the same business outcome and the effort required to maintain them. Review the result as part of the company's regular improvement process, keeping EOS as the operational backbone rather than adding a competing system.

Category: Forward-deployed engineering

← All questions