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, practical architecture, data-driven processes, 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

Experience from real challenges, met with practical solutions.

After two decades in technology and data, I rarely meet a problem for the first time. I have debugged production reality, designed architectures, built teams, sat with customers, shaped product and pricing decisions, and carried execution responsibility. That range gives me a wide base to spot patterns, ask sharper questions, and bring creative answers that still survive the real world. I have seen the same problems from the keyboard, the whiteboard, the customer call, and the leadership table.

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

Services

What I help with

Five practical ways to bring senior creative-technical judgment into messy product, technology, data, and execution situations.

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 validation plan, and a roadmap based on reality rather than 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: a decision roadmap, ownership map, 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 technical decisions that can survive implementation.

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, feedback loops, dashboards, operating reviews, and a shared language for progress.

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: stronger team processes, clearer ownership, better judgment, faster learning, and people who can carry the system forward.

How it all connects

See the whole system — and keep it moving.

Business goals, customer reality, product priorities, data, architecture, engineering, process, and people rarely move in neat lines. The value is in holding the whole picture at once — seeing how every part pulls on the others, finding where it is really stuck, and keeping it flowing from strategy to implementation in a way that survives contact with reality.

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

Start a conversation

or connect on LinkedIn.