人の仕組み
概要 採用と選考 定着 モチベーション
I-Profile
仕組み 採用で使う チームで使う 事業健全性診断
サービス
経営コンサルティング 研修とリーダーシップ 財務管理 営業とマーケティング すべてのサービス
Mind Business School
MBSとは 成果を見る 修了者を見る 学習コース 世界のMBS
無料リソース
無料ガイド ブログ イベント 事業健全性診断
会社情報
私たちについて イベント お問い合わせ 無料診断を予約 パートナーになる
Home/I-Profile/For teams

Capable people, and somehow it does not work.

Every owner recognises the situation: the individuals are good, the team is not. The usual explanation is personality, which leads nowhere because personalities do not change. The useful explanation is nearly always structural.

What you actually see

The same three patterns, in company after company.

01

Everyone decides, nobody decides

A team made up entirely of people who need consensus before moving. Meetings are pleasant, agreement is total, and nothing is ever actually chosen. Adding another meeting makes it worse.

02

Two people who need opposite things

One works best with autonomy and reads any check-in as distrust. The other needs regular contact and reads its absence as being abandoned. Both are reasonable. Together, without knowing this, they will conclude the other one is difficult.

03

The manager runs everyone the same way

Usually the way that would work on themselves. It works on the third of the team who happen to be similar, and quietly demotivates the rest, who are then labelled as the weaker performers.

How the session runs

Everyone is profiled, and everyone sees the map.

This is not an assessment done to a team behind its back. Each person takes I-Profile, each person is shown their own reading, and then the team looks at the map of itself together with a consultant in the room.

The moment that changes things is rarely a revelation about someone else. It is a person recognising their own pattern and realising the colleague they have been quietly annoyed with for a year was not doing it at them.

What comes out of the session is practical: who should own which decision, which pairs need a defined way of working, and what the manager needs to do differently for each person rather than for the team as a block.

Map your team, then look at it together.

Most of what looks like conflict turns out to be two people needing opposite conditions and neither one knowing it.