What Travis is looking for now

Improve workflows with practical systems your team can actually use.

Travis helps organizations redesign real workflows, connect the data those workflows depend on, and build decision-support tools that reduce friction without removing human accountability. His value is in understanding the workflow, the handoffs, the systems of record, the people who own decisions, and the controls required to make automation safe enough to use.

The goal is not to buy more software. The goal is to make the work flow better.

Career input map

Every chapter points toward workflow-first improvement.

When existing SaaS tools are the right answer, use them. When they add cost without fixing the workflow, build the minimum durable system instead.

PhD / Head Tutor

Taught complex material and built an Excel macro sign-in system to replace a clipboard workflow.

Carry forward: workflow automation starts with watching where people lose time.

Tesla

Structured supplier evaluation, requirements gathering, test planning, and lab buildout during hypergrowth.

Carry forward: good decisions require clear requirements and comparable data.

Faraday Future

Architected requirements systems, workflow automations, configuration processes, and enterprise data-flow maps.

Carry forward: systems of record must agree on what is true.

Rivian

Built change-control, traceability, product-configuration, and issue-resolution mechanisms during scale-up.

Carry forward: scale requires rules for information change and approval.

Ampaire

Owned requirements, suppliers, budget, testing, certification strategy, and stakeholder alignment.

Carry forward: safety-critical work requires traceable decisions and clear ownership.

Kyma

Built a company operating model: team, roadmap, headquarters, suppliers, partners, IP, revenue, and execution rhythm.

Carry forward: transformation is the operating system that makes execution possible.

Lucid

Built engineering knowledge and workflow tools combining a structured knowledge base, internal web app, and retrieval support.

Carry forward: useful tools start with workflow design and knowledge architecture.

Workflow Systems

Workflow discovery, data architecture, controls, adoption, and measurement.

Human-Centered Technology

Systems that strengthen judgment, preserve accountability, and improve how people make decisions together.

Transformation model

How Travis Improves Workflows

1

Map the real workflow

Inputs, handoffs, decisions, rework, approvals, tools, owners, and failure points.

2

Find friction

Prioritize high-frequency, high-cost workflows where improvement creates measurable value.

3

Define data

Identify systems of record, ownership, access rules, quality gaps, and integration points.

4

Build minimum durable system

Prototype the lightest app, automation, knowledge base, or integration layer that proves value.

5

Keep humans accountable

Design permissions, review points, audit trails, approvals, and ownership from day one.

6

Measure and scale

Track time saved, cycle time, throughput, quality, adoption, and business value.

Example deep dive

What Faraday Future Taught Travis About Workflow Systems

At Faraday Future, Travis learned how much of an organization's execution quality depends on how information moves between systems. A part-level attribute does not simply live in one place. It moves through product definition, requirements, release, change control, procurement, inventory, manufacturing execution, and ultimately vehicle build.

Travis mapped the flow from PLM into SAP/ERP and MES at an attribute-by-attribute level across release and change-management cycles from prototyping into production. That experience shaped his view of workflow tooling: automation is only useful if it respects the data, ownership, permissions, and state changes behind the workflow it is being asked to support.

Part AttributePLM DefinitionEngineering ReleaseChange ControlSAP / ERPProcurement + InventoryMESQuality Loop

Software can assist this workflow only after the truth path is mapped.

Where Travis can help

Practical workflow improvement without SaaS sprawl.

Workflow discovery

Map end-to-end workflows, define owners, and prioritize where automation or better tooling can create measurable value.

Enterprise data mapping

Connect workflows to PLM, ERP, MES, CRM, Jira, SharePoint, Confluence, knowledge bases, databases, and internal tools.

Tool and platform design

Design supported workflows with clear inputs, outputs, permissions, escalation paths, and human accountability.

Knowledge architecture

Turn fragmented documents and scattered repositories into structured knowledge that people and internal tools can use.

Pilot-to-scale execution

Build quickly, test in real work, measure results, iterate, and scale only what proves value.

Governance and controls

Define decision rights, auditability, review points, data access, and safety controls.

Practical CTA

If your workflows are ready to improve, but your systems are not, Travis can help.

Travis is looking for roles, consulting engagements, and collaborations where he can help businesses turn messy workflows into safe, measurable, software-supported systems.