Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

Why can I design parts but not whole plants?

You can design a reactor. You can design a column, a pump system, a single unit. Give you one piece, and you solve it well. But show you a whole plant, every unit connected, and the picture falls apart. This is not a talent gap. You already have the technical skill. What you lack is a mental map — how parts move together under real heat, flow, pressure, and time. That map is not learned in one course. It is built by tracing whole systems, again and again, until the pattern becomes automatic. Stop waiting to feel ready for complexity. Pick one integrated plant — real, or from your own work — and start tracing its connections today.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
The gap is a missing mental model, so some teaching is needed, but closing it mostly takes repeated practice tracing real systems — more coaching than lecture.
How the two dials adapt to you →
What’s really going on

You do not lack skill. You lack the habit of seeing the whole plant as one body, where every part feeds and limits every other part. Stop studying units in isolation. Choose one integrated system, trace how a change in one corner moves through all of it, and repeat until it becomes instinct.

🔒 What you’ll build togetherUnlock by starting
A moveChoose one plant you already have plans for. Redraw it as a flow of connections, not boxes.
A moveTrace one change — a shift in feed rate, a pressure drop — through the entire system by hand, start to finish.
A moveList every place one unit depends on another. Mark what breaks if that link fails.
A moveBuild a one-page map of the whole plant before you touch a single piece of detailed design.
A moveReview a finished project and ask: where did I think in parts instead of the whole?

What changes unlock by starting

  • You can hold the whole plant in mind, not just its pieces.
  • You spot where one change ripples through the system before it surprises you.
  • You design integration points on purpose, not as an afterthought.
  • You trust your own judgment on complex plants instead of avoiding them.
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.