What I help with

Common design and engineering problems I help solve

Below are some illustrative examples of the design and engineering problems I most often help clients work through. They are there to help you recognise the nearest fit, not to force your situation into a neat box.

In reality, jobs usually span a few of these areas or move naturally between them as the job develops.

Browse below, or use the filters to narrow by engagement mode:

ambiguity Phase 0: Definition & Scoping

bounded outputs Defined-scope Sprint

recurring needs Ongoing Support Retainer

Phase 0: Definition

Problem definition & alignment

Get clarity on the real problem, success criteria, and what to do next.

When a team knows something is wrong but has not yet converged on exactly what needs fixing, work can stall or loop. I help clarify where the real ambiguity sits, align people around the core objective, and define a more credible way forward.

Typical Outputs:

  • A crisp problem statement, with key assumptions noted.
  • A clear definition of done, with what good looks like made explicit.
  • A viable shortlist of paths forward, with risks / unknowns called out.

Approach:

This would typically start with reviewing the material already available — emails, sketches, CAD, notes, test results, supplier comments — and separating symptoms from the underlying decision that needs to be made. I’d then tighten the problem definition, surface the assumptions and constraints that matter, and reduce the position to a small number of viable ways forward.

Typical Inputs:

  • Any existing artifacts – emails, notes, sketches, CAD, mark-ups, photos, or test results etc.
  • A short conversation with the key decision-maker(s) to clarify objectives, constraints, concerns.
  • Any known constraints, like budget limits, technical interfaces, standards, or deadlines.

In practice, problems like this rarely sit in a neat box. This kind of support often blends into requirements definition, concept comparison, or a more bounded delivery Sprint once the situation is clearer.

Phase 0: Definition

Requirements & constraints definition

Turn “we need a thing” into a usable spec engineers and suppliers can act on.

When a team knows something is wrong but has not yet converged on exactly what needs fixing, work can stall or loop. I help clarify where the real ambiguity sits, align people around the core objective, and define a more credible way forward.

Typical Outputs:

  • A crisp problem statement, with key assumptions noted.
  • A clear definition of done, with what good looks like made explicit.
  • A viable shortlist of paths forward, with risks / unknowns called out.

Approach:

This would typically start with reviewing the material already available — emails, sketches, CAD, notes, test results, supplier comments — and separating symptoms from the underlying decision that needs to be made. I’d then tighten the problem definition, surface the assumptions and constraints that matter, and reduce the position to a small number of viable ways forward.

Typical Inputs:

  • Any existing artifacts – emails, notes, sketches, CAD, mark-ups, photos, or test results etc.
  • A short conversation with the key decision-maker(s) to clarify objectives, constraints, concerns.
  • Any known constraints, like budget limits, technical interfaces, standards, or deadlines.

In practice, problems like this rarely sit in a neat box. This kind of support often blends into requirements definition, concept comparison, or a more bounded delivery Sprint once the situation is clearer.

Phase 0: Definition

Design development to manufacturing-ready release

Take a concept to a coherent, buildable release point.

When a team knows something is wrong but has not yet converged on exactly what needs fixing, work can stall or loop. I help clarify where the real ambiguity sits, align people around the core objective, and define a more credible way forward.

Typical Outputs:

  • A crisp problem statement, with key assumptions noted.
  • A clear definition of done, with what good looks like made explicit.
  • A viable shortlist of paths forward, with risks / unknowns called out.

Approach:

This would typically start with reviewing the material already available — emails, sketches, CAD, notes, test results, supplier comments — and separating symptoms from the underlying decision that needs to be made. I’d then tighten the problem definition, surface the assumptions and constraints that matter, and reduce the position to a small number of viable ways forward.

Typical Inputs:

  • Any existing artifacts – emails, notes, sketches, CAD, mark-ups, photos, or test results etc.
  • A short conversation with the key decision-maker(s) to clarify objectives, constraints, concerns.
  • Any known constraints, like budget limits, technical interfaces, standards, or deadlines.

In practice, problems like this rarely sit in a neat box. This kind of support often blends into requirements definition, concept comparison, or a more bounded delivery Sprint once the situation is clearer.

Defined-scope Sprint

Structural analysis (FEA) package

Bounded FEA and structural justification tied to agreed load cases and criteria.

When a team knows something is wrong but has not yet converged on exactly what needs fixing, work can stall or loop. I help clarify where the real ambiguity sits, align people around the core objective, and define a more credible way forward.

Typical Outputs:

  • A crisp problem statement, with key assumptions noted.
  • A clear definition of done, with what good looks like made explicit.
  • A viable shortlist of paths forward, with risks / unknowns called out.

Approach:

This would typically start with reviewing the material already available — emails, sketches, CAD, notes, test results, supplier comments — and separating symptoms from the underlying decision that needs to be made. I’d then tighten the problem definition, surface the assumptions and constraints that matter, and reduce the position to a small number of viable ways forward.

Typical Inputs:

  • Any existing artifacts – emails, notes, sketches, CAD, mark-ups, photos, or test results etc.
  • A short conversation with the key decision-maker(s) to clarify objectives, constraints, concerns.
  • Any known constraints, like budget limits, technical interfaces, standards, or deadlines.

In practice, problems like this rarely sit in a neat box. This kind of support often blends into requirements definition, concept comparison, or a more bounded delivery Sprint once the situation is clearer.

Defined-scope Sprint

Concept selection & trade-offs

Compare options properly and choose a concept with eyes open.

When a team knows something is wrong but has not yet converged on exactly what needs fixing, work can stall or loop. I help clarify where the real ambiguity sits, align people around the core objective, and define a more credible way forward.

Typical Outputs:

  • A crisp problem statement, with key assumptions noted.
  • A clear definition of done, with what good looks like made explicit.
  • A viable shortlist of paths forward, with risks / unknowns called out.

Approach:

This would typically start with reviewing the material already available — emails, sketches, CAD, notes, test results, supplier comments — and separating symptoms from the underlying decision that needs to be made. I’d then tighten the problem definition, surface the assumptions and constraints that matter, and reduce the position to a small number of viable ways forward.

Typical Inputs:

  • Any existing artifacts – emails, notes, sketches, CAD, mark-ups, photos, or test results etc.
  • A short conversation with the key decision-maker(s) to clarify objectives, constraints, concerns.
  • Any known constraints, like budget limits, technical interfaces, standards, or deadlines.

In practice, problems like this rarely sit in a neat box. This kind of support often blends into requirements definition, concept comparison, or a more bounded delivery Sprint once the situation is clearer.

Defined-scope Sprint

Complex CAD modelling package

Lorem ipsum dolor sit amet, consectetuer adipiscing elit.

When a team knows something is wrong but has not yet converged on exactly what needs fixing, work can stall or loop. I help clarify where the real ambiguity sits, align people around the core objective, and define a more credible way forward.

Typical Outputs:

  • A crisp problem statement, with key assumptions noted.
  • A clear definition of done, with what good looks like made explicit.
  • A viable shortlist of paths forward, with risks / unknowns called out.

Approach:

This would typically start with reviewing the material already available — emails, sketches, CAD, notes, test results, supplier comments — and separating symptoms from the underlying decision that needs to be made. I’d then tighten the problem definition, surface the assumptions and constraints that matter, and reduce the position to a small number of viable ways forward.

Typical Inputs:

  • Any existing artifacts – emails, notes, sketches, CAD, mark-ups, photos, or test results etc.
  • A short conversation with the key decision-maker(s) to clarify objectives, constraints, concerns.
  • Any known constraints, like budget limits, technical interfaces, standards, or deadlines.

In practice, problems like this rarely sit in a neat box. This kind of support often blends into requirements definition, concept comparison, or a more bounded delivery Sprint once the situation is clearer.

Ongoing Support

Independent checking, mark-up & feedback

Clean, structured CAD modelling delivered as a bounded package.

When a team knows something is wrong but has not yet converged on exactly what needs fixing, work can stall or loop. I help clarify where the real ambiguity sits, align people around the core objective, and define a more credible way forward.

Typical Outputs:

  • A crisp problem statement, with key assumptions noted.
  • A clear definition of done, with what good looks like made explicit.
  • A viable shortlist of paths forward, with risks / unknowns called out.

Approach:

This would typically start with reviewing the material already available — emails, sketches, CAD, notes, test results, supplier comments — and separating symptoms from the underlying decision that needs to be made. I’d then tighten the problem definition, surface the assumptions and constraints that matter, and reduce the position to a small number of viable ways forward.

Typical Inputs:

  • Any existing artifacts – emails, notes, sketches, CAD, mark-ups, photos, or test results etc.
  • A short conversation with the key decision-maker(s) to clarify objectives, constraints, concerns.
  • Any known constraints, like budget limits, technical interfaces, standards, or deadlines.

In practice, problems like this rarely sit in a neat box. This kind of support often blends into requirements definition, concept comparison, or a more bounded delivery Sprint once the situation is clearer.

Ongoing Support

On-call engineering decision support

Senior-level checking of CAD, drawings, calcs, and analyses to reduce risk.

When a team knows something is wrong but has not yet converged on exactly what needs fixing, work can stall or loop. I help clarify where the real ambiguity sits, align people around the core objective, and define a more credible way forward.

Typical Outputs:

  • A crisp problem statement, with key assumptions noted.
  • A clear definition of done, with what good looks like made explicit.
  • A viable shortlist of paths forward, with risks / unknowns called out.

Approach:

This would typically start with reviewing the material already available — emails, sketches, CAD, notes, test results, supplier comments — and separating symptoms from the underlying decision that needs to be made. I’d then tighten the problem definition, surface the assumptions and constraints that matter, and reduce the position to a small number of viable ways forward.

Typical Inputs:

  • Any existing artifacts – emails, notes, sketches, CAD, mark-ups, photos, or test results etc.
  • A short conversation with the key decision-maker(s) to clarify objectives, constraints, concerns.
  • Any known constraints, like budget limits, technical interfaces, standards, or deadlines.

In practice, problems like this rarely sit in a neat box. This kind of support often blends into requirements definition, concept comparison, or a more bounded delivery Sprint once the situation is clearer.

FAQ’s

Quick answers on what I help with — and which mode fits.

A. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus.

Donec quam felis, ultricies nec, pellentesque eu, pretium quis, sem. Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec, vulputate eget, arcu.

In enim justo, rhoncus ut, imperdiet a, venenatis vitae, justo. Nullam dictum felis eu pede mollis pretium. Integer tincidunt. Cras dapibus. Vivamus elementum semper nisi. Aenean vulputate eleifend tellus. Aenean leo ligula, porttitor eu, consequat vitae, eleifend ac, enim. Aliquam lorem ante, dapibus in, viverra quis, feugiat a.

Contact

If you need to solve a problem and you’d like to explore whether I can help, drop me an email:

What to include

To help me give you a useful reply, please mention…

  • What you’re building or dealing with (one or two sentences)
  • What’s going wrong, or what decision you’re trying to make
  • Key constraints (budget, timescale, materials, interfaces, standards)
  • What information you already have (CAD, drawings, photos, etc)
  • Desired outcome (e.g. options report, CAD pack, calcs, FEA etc)
  • Any deadlines and why they exist (so I can reality-check them)

Attachments

Attachments are welcome:

  • All enquiries and attachments are treated as confidential by default
  • If attachments are over 2MB, please use a file-sharing service such as Dropbox or WeTransfer and include a download link.

What happens next?

I’ll usually reply with a quick fit-check…

If it's a fit:

  • I’ll tell you whether and how I can help
  • I’ll give you some options for how we could move forward
  • I’ll ask for the minimum info needed to scope it

If it's not a fit:

  • I’ll say so and tell you why
  • I may suggest an alternative route, if appropriate

Email me directly at:

hello@frugaldesign.co.uk
Compose email