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

Why do the new machine's extra features still trip me up?

You call yourself handy. That's true of what you already know. The new equipment has features you skip past, and you tell yourself they're extra, not essential. That's a comfortable story, and comfortable stories are usually false. Here's the truth: you haven't used those features because no one has made you, and you haven't asked your pod to help you close the gap. A skill you don't use is a skill you don't have, no matter how long you've owned the manual. This isn't about mastering every button alone, at night, out of guilt. It's about your team deciding together which features actually matter for your work, and teaching each other before a real case forces the lesson on you.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
A little to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The gap here isn't understanding — it's the choice to open the manual and ask for help, so coaching carries more weight than teaching.
How the two dials adapt to you →
What’s really going on

You avoid those features because avoiding them is easy, not because they don't matter. The machine doesn't care about your excuse. Pick one feature this week. Find the teammate who already uses it. Learn it beside them, on a real case. That is the whole task.

🔒 What you’ll build togetherUnlock by starting
A movePick one unused feature today. Name the actual case where it would matter.
A moveFind the teammate who already uses it. Ask them to walk you through it this week, not someday.
A moveTrack every time you skip a feature out of habit instead of real need.
A moveOnce you've used a feature twice, teach it back to your pod.
A moveSet a date with your team to review which features remain unused, and why.
PractiseFeature Audit · a Pod of 4 · 30 min

What changes unlock by starting

  • You use a previously-skipped feature on a real case within two weeks.
  • Your pod knows who is strong on which feature, so no one guesses anymore.
  • You stop mistaking comfort with old tools for competence with new ones.
  • Avoidance becomes something you name out loud, not something you hide.
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.