Creative problem-solving

Solve what matters.
Build what works.

Illustrated portrait — Mozart and Ben-Gurion, composition meeting decision.
Composition meets decision

I help founders, leaders, and teams turn business and technology challenges into clear decisions, systems that hold up, stronger teams, and measurable progress.

Start a conversation See what I help with

No photo of me — the first impression is better in a conversation.

Experience

I’ve been on every side of the table.

After two decades in technology and data, I rarely meet a problem for the first time. I’ve worked close to the code, close to the customer, and close to the leadership table — which helps me connect problems that look unrelated, cut through complexity, and move teams toward decisions that hold up in the real world. The hardest problems are rarely technical. They sit where business, product, engineering, and people meet. That’s where I do my best work.

Some of where I’ve worked & who I’ve worked with

Services

Where I usually get involved

In practice, it’s usually one of these five.

Line-art garden and doorway scene representing discovery and direction.

I

Direction, strategy & validation

Clarify what matters, what problem is worth solving, which opportunity deserves attention, and what needs to be learned before committing serious resources.

Outcome: sharper choices, a clear validation plan, and a roadmap built on reality instead of noise.

Line-art field and water tower scene representing decision making and execution.

II

Decisions & execution

Move leaders and teams from ambiguity, loops, and endless discussion into decisions, ownership, priorities, and practical action.

Outcome: the key decisions made, clear ownership, agreed priorities, and a path the team can actually execute.

Line-art infrastructure and water channel representing architecture and data flow.

III

Technology, data & AI architecture

Design the architecture behind the product: systems, data flows, integrations, AI components, scale, performance, reliability, cost, and the tradeoffs between them.

Outcome: practical architecture, clear tradeoffs, a build sequence, and a technical direction the team won’t have to rebuild in six months.

Line-art interior conversation scene representing measurement and operating signals.

IV

Data-driven processes & measurement

Define what should be measured, how it should be measured, which signals matter, and how data becomes part of decision-making instead of decoration.

Outcome: a metrics model, dashboards people actually use, working feedback loops, and everyone deciding from the same numbers instead of arguing about them.

Line-art workshop and group scene representing mentoring and team work.

V

Team operating system & mentoring

Build the team habits, rituals, ownership patterns, mentoring structures, and cross-functional processes that make better execution repeatable.

Outcome: clearer ownership, better mentoring, fewer things slipping through the cracks, and a team that depends less on any one person.

How it all connects

It’s rarely just one problem.

Product is optimizing for one thing, engineering for another. The data points one way, the customer pulls another, and leadership is weighing something else again. Everyone can be right from where they sit — and the system still gets stuck between them.

The work isn’t to optimize each part on its own. It’s to hold the whole picture at once, see how the pieces pull on each other, find the few decisions that move everything forward, and help turn those into execution.

The whole system in one view Business Customers Product Data Architecture Technology People Process Engineering

When to call me

Call me when the problem sits between business, product, technology, data, people, and execution — and one more meeting will not solve it.

  1. 01Everyone has a solution — but nobody agrees on the actual problem.
  2. 02You have too many ideas and no clear decision.
  3. 03The team is busy, but progress is hard to see.
  4. 04Product, technology, data, and business are not aligned.
  5. 05You need creativity and execution in the same room.
  6. 06You need technical architecture, but also business and product judgment.
  7. 07You are building something new inside an existing company.
  8. 08You want decisions grounded in data, but you are not sure how to get there — or whether the data you have can be trusted.
  9. 09You want stronger team processes, ownership, mentoring, and execution habits.
  10. 10You need to validate a direction before committing serious resources.
  11. 11The business is growing and you need to scale, but the platform has become the bottleneck.

Let’s talk about what you’re trying to build, fix, validate, or decide.

Bring the messy situation, the open decision, the architecture question, the team process that is not working, or the opportunity you need to validate.

I don’t come with a methodology. I come to understand the problem, help make the decisions, and see them through.

Start a conversation

or connect on LinkedIn.