Early Technology Development
Advanced engineering before teams knew exactly what the product needed to be.
Turning complexity into clear objectives and following through with discipline and skill.
e.g. “The strategy was two slides. The execution took two years.”

Hi, I’m Tim. I’ve spent my career helping emerging technologies move from technical promise to market reality.
At Mercedes-Benz R&D, I worked across hydrogen fuel cells and automotive batteries, connecting technical development, partnerships, and operations to decisions the larger organization could use.
Today, I bring that experience to founders, executives, and technical teams.
Simple Not Easy is my consulting practice for leaders and technical teams pursuing ambitious goals.
It grew from twenty years of organizing people, decisions, and technical programs around clear missions: “find a better battery chemistry” or “make a hydrogen vehicle succeed in global markets.”
When I started, hydrogen fuel cells and battery-powered vehicles were both grouped under “alternative energy.” My work across these fields took recurring forms:
Advanced engineering before teams knew exactly what the product needed to be.
Defining, negotiating, and guiding technical programs with startups and suppliers.
Building laboratory capabilities for chemistry evaluation and investigating high-voltage battery-pack field failures.
Deciding which emerging technologies deserved resources and when priorities needed to change.
Bringing global experts together to advance emerging technologies such as lithium-metal anodes, and developing technical standards through SAE.
Designing, building, and maintaining automated engineering analysis tools that surfaced what engineers needed to know.
Hard technical work rarely stalls because people do not care. It usually stalls because the direction is fuzzy, the decision process is overcomplicated, or the hard conversations keep getting delayed.
The same questions kept returning: What matters? What decision comes next? What does the team need to move forward?
Be specific about what matters, what is uncertain, and what decision needs to be made.
Do the work that moves the objective forward, not the meetings, decks, and rituals that merely look like progress.
Build frameworks and habits that let teams deliver without constant intervention or heroics.