Tescam

OP 10

Context

Bridgestone’s mechanical engineers test tires — a rigorous, regulated process with real safety weight behind every result. The work was being coordinated through scattered Excel sheets and workflows that lived in people’s heads.

I designed the web application from scratch and carried it as product owner. Research, definition, design, and the decisions in between.

OP 20

Problem

When critical procedures run on spreadsheets, the data is only as reliable as the last person who touched the file. Scheduling, data collection, and approvals were disconnected, and there was no single structured record of what had been tested and signed off.

OP 30

Process

I sat with the engineers to understand the testing procedures as they actually happen, not as an org chart imagines them. From there I structured the tool around the real sequence — scheduling, execution, data capture, and approval — with the states and permissions that a regulated process needs.

OP 40

Outcome

Testing moved off improvised spreadsheets and onto a purpose-built application. A single structured place to schedule procedures, collect data, and manage approvals — with a clear, auditable trail of what happened and who signed it.