<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
  <title>P2O Consulting — Writing</title>
  <subtitle>Notes on drag, flow and how work actually moves.</subtitle>
  <link href="https://p2o.work/feed.xml" rel="self" />
  <link href="https://p2o.work/" />
  <updated>2026-09-09T00:00:00Z</updated>
  <id>https://p2o.work/</id>
  <author>
    <name>Ade Nichols</name>
    <email>hello@p2o.work</email>
  </author>
  <entry>
    <title>Beyond hard and soft skills</title>
    <link href="https://p2o.work/writing/beyond-hard-and-soft-skills/" />
    <updated>2026-09-09T00:00:00Z</updated>
    <id>https://p2o.work/writing/beyond-hard-and-soft-skills/</id>
    <content type="html">&lt;p&gt;Most job descriptions still split people into hard skills and soft skills. Most
training budgets are spent along the same seam. Cold technicians and warm
communicators, one column each, and a promotion process that quietly rewards
the first.&lt;/p&gt;
&lt;p&gt;It has been the default for decades and it is wrong in a way that costs you
specific, nameable things.&lt;/p&gt;
&lt;p&gt;Competence has three parts, not two. They are coupled, which means removing any
one of them produces a person you have already worked with, and probably
managed.&lt;/p&gt;
&lt;h2 id=&quot;why-two-was-never-enough&quot;&gt;Why two was never enough&lt;/h2&gt;
&lt;p&gt;I was listening to Dave Snowden recently making the case for the trilectic. In
a complex system, two opposing concepts are rarely enough to think with. A
binary gives you a spectrum and a deadlock. You need a third term to break it
and let the thing move.&lt;/p&gt;
&lt;p&gt;He is not the first to find this. Lefebvre and Soja did the same for space when
they refused the split between the physical and the mental and added the lived.
The pattern repeats because two-part models are easy to hold and poor at
describing anything that behaves like a system.&lt;/p&gt;
&lt;p&gt;Human capability behaves like a system. So here is the third term, and the two
you already know, described properly.&lt;/p&gt;
&lt;h2 id=&quot;bounded-execution&quot;&gt;Bounded execution&lt;/h2&gt;
&lt;p&gt;This is what we have been calling hard skills. The disciplined application of
known rules inside a clear boundary. Writing syntax. Running a financial model.
Configuring a network. Reading a balance sheet.&lt;/p&gt;
&lt;p&gt;This is where human energy converts to value with the least loss. The inputs
are known, the constraints are known, and if you do the work well you get a
predictable output.&lt;/p&gt;
&lt;p&gt;It is the baseline. It is also nothing more than the baseline. Strength without
coordination is someone who can lift a great deal and fall over regularly.&lt;/p&gt;
&lt;h2 id=&quot;interpersonal-calibration&quot;&gt;Interpersonal calibration&lt;/h2&gt;
&lt;p&gt;This is what we have been calling soft skills, usually with a faint apology in
the voice. Empathy. Listening. Reading the room. Nice to have, HR will run a
course.&lt;/p&gt;
&lt;p&gt;Go back to the first law of thermodynamics. Energy cannot be created or
destroyed, only transferred or transformed. Effort that does not become value
becomes something else, and in a team that something is heat. Miscommunication.
Ego. Ambiguous handoffs. The Slack argument on a Friday afternoon that everyone
is still carrying on Monday.&lt;/p&gt;
&lt;p&gt;Interpersonal calibration is the competence that keeps effort converting into
value rather than transforming into friction. It is not a courtesy and it is
not a personality trait. A team with it has working joints. A team without it
has bone grinding on bone, and every movement costs more than it should.&lt;/p&gt;
&lt;h2 id=&quot;adaptive-competence&quot;&gt;Adaptive competence&lt;/h2&gt;
&lt;p&gt;Here is the part the binary cannot see.&lt;/p&gt;
&lt;p&gt;Most training builds linear adaptation: tuning a skill to handle small shifts
inside its own domain. The statistician learns a new package to run the same
analysis. Useful, and not enough.&lt;/p&gt;
&lt;p&gt;Complex environments demand something biologists call exaptation. A capability
built for one purpose gets redeployed against an unrelated problem, because the
underlying shape of the two problems turns out to be the same. An
epidemiologist&#39;s contact-tracing model maps how risk cascades through a banking
network. Nothing about the skill changed. The problem changed, and the skill
fitted anyway.&lt;/p&gt;
&lt;p&gt;Blockbuster is the counter-example everybody reaches for. Nine thousand stores&#39;
worth of bounded execution and not an ounce of adaptive competence when the
ecosystem moved to streaming. Worth being precise about what failed there,
because it is usually described as a strategy problem. It was not. The
capability was present and the ability to redeploy it was not.&lt;/p&gt;
&lt;p&gt;Nobody acquires a skill with foresight about where it will be exapted. The
people who solve unfamiliar problems are carrying a store of capability built
for something else entirely, and they are willing to test its fit when the
pressure changes.&lt;/p&gt;
&lt;h2 id=&quot;three-failure-modes&quot;&gt;Three failure modes&lt;/h2&gt;
&lt;p&gt;Because the three are coupled, taking one away produces a recognisable person.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Missing adaptive competence gives you the stagnant specialist.&lt;/strong&gt; Excellent
execution, good with people, paralysed the moment the domain moves. This is
the person promoted on the strength of a job whose parameters then changed
entirely, and who is now failing in public at something nobody has
acknowledged is a different job.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Missing calibration gives you the isolated executioner.&lt;/strong&gt; Brilliant at the
work, brilliant at the cross-domain leap, and generating so much heat that
nobody can work alongside them long enough for any of it to scale. Every
handoff costs more than it should. Teams reorganise around them rather than
with them.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Missing bounded execution gives you the abstract visionary.&lt;/strong&gt; Wonderful
connections, charming in the client meeting, and no disciplined output at the
end of it. Ideas that never harden into anything anyone can use.&lt;/p&gt;
&lt;p&gt;You have worked with all three. You may have been one of them.&lt;/p&gt;
&lt;h2 id=&quot;why-they-are-coupled&quot;&gt;Why they are coupled&lt;/h2&gt;
&lt;p&gt;Read them together and the coupling is obvious.&lt;/p&gt;
&lt;p&gt;Calibration lowers the cost of exaptation, because a cross-domain leap only
lands if other people accept it. Bounded execution limits which exaptations
are available at all, because you can only transfer a skill you hold at depth.
And adaptive competence needs somewhere to happen: a team running at full
velocity has no margin in which to attempt the leap, which is why the busiest
teams are so often the most stagnant.&lt;/p&gt;
&lt;p&gt;That last one matters more than it looks. Competence is not just a property of
the person. It is a property of the person and the conditions they are working
in.&lt;/p&gt;
&lt;h2 id=&quot;where-this-actually-lives&quot;&gt;Where this actually lives&lt;/h2&gt;
&lt;p&gt;The binary survives because it describes individuals, and individuals are what
we recruit, appraise and promote. Two columns, one person, tick the boxes.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;An organisation does not get the competence its people have. It gets the
competence its structure allows them to use.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Adaptive competence needs slack, and slack is a structural decision.
Calibration builds through repetition. People need to learn each other, and
every reorganisation resets that to zero. Bounded execution is the only one of
the three that survives a badly designed organisation intact, which is
precisely why badly designed organisations end up valuing it above everything
else. It is the part that still works when nothing else does.&lt;/p&gt;
&lt;p&gt;So when a company tells me it has a capability problem, the interesting
question is rarely whether the people are good enough. It is which of these
three the organisation has quietly made impossible.&lt;/p&gt;
&lt;h2 id=&quot;what-to-do-with-this&quot;&gt;What to do with this&lt;/h2&gt;
&lt;p&gt;Stop assessing people on a two-column checklist. Competence is execution,
calibration and transfer, and it is all three or it is none. Pick two and you
have named your next failure mode.&lt;/p&gt;
&lt;p&gt;Then ask the harder question. Look at the three, and work out which one your
organisation is currently arranged to prevent.&lt;/p&gt;
</content>
  </entry>
</feed>