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

I only know one way to work with clients — how do I choose?

You trained in one way of working. It served you once, so now it serves every client — whether it fits or not. That is the honest shape of the problem. This is not a gap in hidden knowledge. Most times, you already sense when a client needs something your method cannot give. You ignore that sense, because changing course means admitting your one tool has edges. Working with others gives you something you do not have alone: eyes on the same client that are not yours. Use them. Someone in your pod will see the mismatch before you do, if you let them look and you let yourself hear it.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The shortage is less about missing frameworks and more about facing what you already notice and avoid acting on.
How the two dials adapt to you →
What’s really going on

You do not lack a method. You lack the habit of asking what this client needs before reaching for your tool. Stop asking 'what do I know how to do.' Start asking 'what does this problem in front of me require.' Choose the need first. Fit your method to it, not the other way around.

🔒 What you’ll build togetherUnlock by starting
A moveBefore your next session, write the client's need in their own words, not yours.
A moveName two other approaches you've seen used, even ones you don't practice, and say when each fits better than yours.
A moveBring your pod one case where you forced your method onto a client who needed something else.
A moveWhen a client resists, treat it as information about fit, not a failure to push harder.
A movePick one client whose need outgrows your method, and refer or defer them this week. Watch what happens.
PractiseFit or Force · a Pod of 4 · 30 min

What changes unlock by starting

  • You catch yourself reaching for your default method, and you pause before applying it.
  • Your pod names mismatches you would have missed alone.
  • You build a short, honest list of signs that mean 'this is not my method's job.'
  • Clients who don't fit your approach get redirected sooner, not after months of friction.

Related problems

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.