Coachability is not a trait you can read off a questionnaire. It is a pattern you observe over a few deliberate attempts, which is a thing you can actually set up.
Coachability is not a fixed trait a manager can read from a CV, interview, or personality questionnaire. It is a pattern observed over a few clear feedback attempts: the person hears the point, understands the expected change, tries a different behaviour, and improves enough to justify continued coaching.
The problem usually appears after the excitement of hiring has passed. The CV showed ownership. The interview sounded composed. The person now misses context, needs more checking than expected, or repeats the same avoidable mistake.
At this size the gap is felt within weeks rather than quarters. There may be no layer of managers to absorb it. The new joiner may own sales operations, customer success, finance, marketing, or delivery. If they operate two levels below the role, the founder feels it by Thursday.
The first question is not whether they are a bad hire. The better question is: is this employee coachable in this role, with this manager, at this stage of the company. That question needs a fair test. Not a mood. Not a label. Not a private verdict formed after one irritating meeting.
A person is not coachable because a questionnaire says so. A person is not uncoachable because they score high or low on a personality dimension. Coachability is a working pattern between feedback and changed behaviour.
A profile may help with a smaller question: how should feedback be delivered to this person so they can use it. Someone may need written examples before a conversation. Someone else may need the conversation first, then a written summary. Some people respond well to direct challenge. Others shut down unless the sequence is specific, private, and calm.
That is not a prediction that feedback will land. It is preparation for how to give feedback with less waste. The output is decision support, never automated decisions. A human manager still has to observe the next piece of work.
The aim is to stop circling the same concern in Slack, stand-ups, and founder conversations. Pick one behaviour that matters to the role. Do not test five behaviours at once. A fair test needs one expectation, three attempts, and notes written soon after each attempt.
Three attempts is not magic. It is just enough structure to separate irritation from evidence. It also protects the employee from vague disappointment. They should know what is being tested before the manager decides the test has failed.
Someone can look junior because the business is new to them. That is different from not absorbing feedback. The distinction matters. One calls for coaching. The other may call for a role decision.
| Still learning the job | Feedback is not being absorbed |
|---|---|
| They ask basic questions once, then stop needing the same answer. | They ask the same question after the same answer has been given clearly. |
| Their first version is rough, but the second version uses the specific feedback. | Their second version repeats the same missing piece or behaviour. |
| They can explain what good looks like, even if they cannot yet produce it consistently. | They cannot restate the expectation after it has been discussed. |
| They make new mistakes as the work gets harder. | They make the same avoidable mistake in the same setting. |
| They surface uncertainty early: “I am not sure how to handle this client risk.” | They hide uncertainty until the deadline or the client exposes it. |
| They accept the example, even if they feel disappointed. | They turn every example into an exception, a defence, or a debate about tone. |
| They improve when the manager changes the format of feedback. | They do not change when feedback is specific, private, timely, and repeated. |
Before deciding that someone lacks coachability, inspect the feedback they have received. Many managers say they have been clear when they have only been frustrated. The employee hears “be more commercial” or “own the process” and has to guess what behaviour should change by Monday.
Vague feedback produces vague correction. “You need to be more proactive” is not a usable instruction. “When a customer has not replied for two days, send one follow-up and flag the account in the renewal channel” is usable. One is a judgement. The other is a behaviour.
Public feedback also distorts the test. Some people can process criticism in a group. Others spend the whole moment managing embarrassment. If the only feedback is given in stand-up, the manager may be testing social composure, not coachability.
Written-only feedback can fail in the opposite direction. A long message may be read as a record for a future dismissal, not as help. Some people need a short conversation first, then three bullets they can act on. Others need the document before they can think clearly. The format matters.
Feedback with no example attached is the most common failure. “Your judgement is off” leaves the person nowhere to stand. “You approved a refund without checking the account history; in this role I need you to check the last two invoices before approving refunds over the agreed threshold” gives them a next move. If the manager cannot name the example, the manager may not be ready to give the feedback.
For a practical way to turn profiles into better weekly conversations, read the management guide. Use profiles in day-to-day management
HyperPersonal AI uses the public-domain IPIP-300 item pool. It measures 5 domains and 30 facets. Scores are continuous dimensions, never types or categories. That matters because people are not sorted into boxes such as coachable, difficult, team player, or lone wolf.
For coachability, the profile should be used narrowly. It may suggest that feedback should be direct and brief. It may suggest that the person will process feedback better with time to reflect. It may suggest that a manager should separate emotional reassurance from operational correction. These are starting points for a conversation between people — not predictions about who will improve.
The organisational portal reads a candidate or employee profile against a role the company has defined. A candidate shares a profile only by an explicit, revocable grant. The profile remains theirs. The organisation sees it because the person permits that access, and the person can revoke it.
For more on adapting management style without turning people into types, use this guide. Manage different personality patterns without labels
Sometimes the fair test fails. The person heard the feedback. The examples were specific. The format was adjusted. The same behaviour still repeats in work that the role must handle. At that point, the honest decision may be that this role is not a fit.
That is not a verdict the software gives you. It is a management decision. Make it early enough that the company is not pretending, and the employee is not being allowed to fail in slow motion. A small company pays twice for delayed honesty: once in the work, and once in the manager attention spent rescuing it.
The next step may be a tighter role, a different manager, a performance plan, or an exit. The right choice depends on the work, the timing, the person, and the company’s capacity to support them. The wrong choice is to keep calling the person uncoachable while giving unclear feedback and hoping the situation resolves itself.
After three attempts, you should have a small record: the behaviour, the example, the feedback format, the employee’s response, and the next piece of work. That record gives the manager something better than a feeling. It also gives the employee a fair account of what was expected and what happened next.
This is the point of treating coachability as observed behaviour. It slows down blame. It also stops managers from carrying avoidable doubt for months. The question is not “do I like coaching this person?” The question is “does feedback change the work enough for this role?”
No. Coachability is observed through feedback and changed behaviour. A personality profile may suggest how feedback is best delivered, but it does not measure or predict whether the person will absorb it.
Use three deliberate attempts for one important behaviour. That gives enough structure to test whether the person can hear, understand, and apply feedback without turning the process into months of drift.
Record the example, the expected behaviour, the format of feedback, the employee’s response, and the next observed piece of work. Keep it factual. Do not write a character assessment.
One argument does not prove low coachability. Look at whether they can later restate the expectation and change the work. Some people process feedback by testing it first.
Yes. Vague, public, or example-free feedback can make a person look uncoachable. A fair test includes changing the manager’s delivery before judging the employee’s response.
If you want to test this on a live role with CV structure, candidate-owned profiles, and manager-facing decision support, start with a small pilot. Run a pilot on a real role
Operated by Alano Tech Pte. Ltd., Singapore.
Terms of Service Privacy Policy
Also from us: Alano.ai Opptymizer Omu Labs