Johari Window

Thinking Tools1.1 Describing the Situation

Developed by Joseph Luft and Harrington Ingham (The Johari Window, a Graphic Model of Interpersonal Awareness, 1955).

A two-by-two grid of what a person knows about themselves against what others know, showing where feedback and disclosure would widen the shared picture.

Eight things about a new team lead, sorted by who knows them

Each note says who already knows the trait: the lead, her team, both, or neither. Place each in its pane; the panel says how it could move. Feedback moves a trait from blind to open, disclosure from hidden to open, and the open pane is where the team works best. The first is placed as an example. Illustrative.

Items (select one, then a box)
  • Not placedPlacedOpenBlindHiddenUnknown
  • Not placedPlacedOpenBlindHiddenUnknown
  • Not placedPlacedOpenBlindHiddenUnknown
  • Not placedPlacedOpenBlindHiddenUnknown
  • Not placedPlacedOpenBlindHiddenUnknown
  • Not placedPlacedOpenBlindHiddenUnknown
  • Not placedPlacedOpenBlindHiddenUnknown
  • Not placedPlacedOpenBlindHiddenUnknown

Known to the team

Team knowsTeam does not know
Blind
Open
Unknown
Hidden
She does not knowShe knows

Known to her

Strong architect. She knows it, and the team says so in every design review.Not placed yet.Strong architect. She knows it, and the team says so in every design review.Open: Known to her and to the team. Work here goes fastest; the aim is to make this pane larger.Open: the team brings her design questions without being asked.Strong architect. She knows it, and the team says so in every design review.Blind: The team sees it and she does not. Feedback moves it to the open pane, if she asks and they feel safe to answer.Strong architect. She knows it, and the team says so in every design review.Hidden: She knows it and the team does not. Disclosing it moves it to the open pane, at a pace she chooses.Strong architect. She knows it, and the team says so in every design review.Unknown: Nobody knows it yet. New work and shared experience bring it out, often into the blind or hidden pane first.Likes written updates. She asked for them on day one, and the team writes them.Not placed yet.Likes written updates. She asked for them on day one, and the team writes them.Open: Known to her and to the team. Work here goes fastest; the aim is to make this pane larger.Open, and working.Likes written updates. She asked for them on day one, and the team writes them.Blind: The team sees it and she does not. Feedback moves it to the open pane, if she asks and they feel safe to answer.Likes written updates. She asked for them on day one, and the team writes them.Hidden: She knows it and the team does not. Disclosing it moves it to the open pane, at a pace she chooses.Likes written updates. She asked for them on day one, and the team writes them.Unknown: Nobody knows it yet. New work and shared experience bring it out, often into the blind or hidden pane first.Interrupts at standup. Three engineers mention it to each other. She has no idea.Not placed yet.Interrupts at standup. Three engineers mention it to each other. She has no idea.Open: Known to her and to the team. Work here goes fastest; the aim is to make this pane larger.Interrupts at standup. Three engineers mention it to each other. She has no idea.Blind: The team sees it and she does not. Feedback moves it to the open pane, if she asks and they feel safe to answer.Blind. At the retrospective she asks what to change, and it moves to open; standups get shorter.Interrupts at standup. Three engineers mention it to each other. She has no idea.Hidden: She knows it and the team does not. Disclosing it moves it to the open pane, at a pace she chooses.Interrupts at standup. Three engineers mention it to each other. She has no idea.Unknown: Nobody knows it yet. New work and shared experience bring it out, often into the blind or hidden pane first.Messages at midnight. She writes late because it suits her; the team reads it as expecting replies.Not placed yet.Messages at midnight. She writes late because it suits her; the team reads it as expecting replies.Open: Known to her and to the team. Work here goes fastest; the aim is to make this pane larger.Messages at midnight. She writes late because it suits her; the team reads it as expecting replies.Blind: The team sees it and she does not. Feedback moves it to the open pane, if she asks and they feel safe to answer.Blind. Once told, she schedules messages for the morning.Messages at midnight. She writes late because it suits her; the team reads it as expecting replies.Hidden: She knows it and the team does not. Disclosing it moves it to the open pane, at a pace she chooses.Messages at midnight. She writes late because it suits her; the team reads it as expecting replies.Unknown: Nobody knows it yet. New work and shared experience bring it out, often into the blind or hidden pane first.Nervous with execs. She dreads the monthly executive review and has told no one.Not placed yet.Nervous with execs. She dreads the monthly executive review and has told no one.Open: Known to her and to the team. Work here goes fastest; the aim is to make this pane larger.Nervous with execs. She dreads the monthly executive review and has told no one.Blind: The team sees it and she does not. Feedback moves it to the open pane, if she asks and they feel safe to answer.Nervous with execs. She dreads the monthly executive review and has told no one.Hidden: She knows it and the team does not. Disclosing it moves it to the open pane, at a pace she chooses.Hidden. When she says so, a senior engineer offers to co-present.Nervous with execs. She dreads the monthly executive review and has told no one.Unknown: Nobody knows it yet. New work and shared experience bring it out, often into the blind or hidden pane first.Unsure of the roadmap. She privately doubts the second-half roadmap.Not placed yet.Unsure of the roadmap. She privately doubts the second-half roadmap.Open: Known to her and to the team. Work here goes fastest; the aim is to make this pane larger.Unsure of the roadmap. She privately doubts the second-half roadmap.Blind: The team sees it and she does not. Feedback moves it to the open pane, if she asks and they feel safe to answer.Unsure of the roadmap. She privately doubts the second-half roadmap.Hidden: She knows it and the team does not. Disclosing it moves it to the open pane, at a pace she chooses.Hidden. Sharing the doubt early lets the team help test it before it is committed.Unsure of the roadmap. She privately doubts the second-half roadmap.Unknown: Nobody knows it yet. New work and shared experience bring it out, often into the blind or hidden pane first.Crisis leadership. The team has not had an outage since she joined.Not placed yet.Crisis leadership. The team has not had an outage since she joined.Open: Known to her and to the team. Work here goes fastest; the aim is to make this pane larger.Crisis leadership. The team has not had an outage since she joined.Blind: The team sees it and she does not. Feedback moves it to the open pane, if she asks and they feel safe to answer.Crisis leadership. The team has not had an outage since she joined.Hidden: She knows it and the team does not. Disclosing it moves it to the open pane, at a pace she chooses.Crisis leadership. The team has not had an outage since she joined.Unknown: Nobody knows it yet. New work and shared experience bring it out, often into the blind or hidden pane first.Unknown to everyone until the first incident.Budgeting skill. She has never owned a budget, and the team has never seen one from her.Not placed yet.Budgeting skill. She has never owned a budget, and the team has never seen one from her.Open: Known to her and to the team. Work here goes fastest; the aim is to make this pane larger.Budgeting skill. She has never owned a budget, and the team has never seen one from her.Blind: The team sees it and she does not. Feedback moves it to the open pane, if she asks and they feel safe to answer.Budgeting skill. She has never owned a budget, and the team has never seen one from her.Hidden: She knows it and the team does not. Disclosing it moves it to the open pane, at a pace she chooses.Budgeting skill. She has never owned a budget, and the team has never seen one from her.Unknown: Nobody knows it yet. New work and shared experience bring it out, often into the blind or hidden pane first.Unknown. Next year's planning will show it.

Your sort matched 0 of 8.Your sort matched 1 of 8.Your sort matched 2 of 8.Your sort matched 3 of 8.Your sort matched 4 of 8.Your sort matched 5 of 8.Your sort matched 6 of 8.Your sort matched 7 of 8.Your sort matched 8 of 8.

Open
Known to her and to the team. Work here goes fastest; the aim is to make this pane larger.
Blind
The team sees it and she does not. Feedback moves it to the open pane, if she asks and they feel safe to answer.
Hidden
She knows it and the team does not. Disclosing it moves it to the open pane, at a pace she chooses.
Unknown
Nobody knows it yet. New work and shared experience bring it out, often into the blind or hidden pane first.

The sort

  • Strong architect: Open. Open: the team brings her design questions without being asked.
  • Likes written updates: Open. Open, and working.
  • Interrupts at standup: Blind. Blind. At the retrospective she asks what to change, and it moves to open; standups get shorter.
  • Messages at midnight: Blind. Blind. Once told, she schedules messages for the morning.
  • Nervous with execs: Hidden. Hidden. When she says so, a senior engineer offers to co-present.
  • Unsure of the roadmap: Hidden. Hidden. Sharing the doubt early lets the team help test it before it is committed.
  • Crisis leadership: Unknown. Unknown to everyone until the first incident.
  • Budgeting skill: Unknown. Unknown. Next year's planning will show it.

An example

Three months after an engineering lead joined a payments team, the team's pulse survey dropped and nobody could say why. Her manager suggested a session built on a four-pane window.

She and her team each wrote traits and habits on cards, then sorted them by who knew what. Some were open to all: she was strong on architecture and liked written updates. Some she had never seen: she cut people off at standup, and her midnight messages read as demands for replies. Some only she knew: she dreaded the monthly executive review and privately doubted the roadmap for the second half. Two nobody knew yet, because there had been no outage and no budget.

She asked for the blind ones out loud, and the team gave them. She disclosed two hidden ones, and a senior engineer offered to co-present at the executive review. Standups got shorter, messages moved to the morning, and the roadmap doubt became a test in the next sprint. The next survey recovered most of the drop.

Why it works

Working relationships run on what both people know. When a habit is visible to everyone except the person who has it, or a worry is known only to the person who has it, the team works around it without saying so, and the cost shows up as friction nobody can name.

The window separates the two gaps and gives each its own fix. The blind pane shrinks only through feedback, so the person has to ask and the team has to feel safe answering. The hidden pane shrinks only through disclosure, which the person controls. Naming the panes gives a team words for both moves, so asking for feedback and sharing a doubt become ordinary acts instead of risky ones, and the open pane grows.

The thinking behind it

Joseph Luft Joseph Luft, an American psychologist, devised the Johari window with Harrington Ingham and presented it in The Johari Window, a Graphic Model of Interpersonal Awareness (1955), in the proceedings of the Western Training Laboratory in Group Development at UCLA. The model is a four-pane picture of what is known and unknown about a person to the self and to others, and was built for group development training.

Harrington Ingham Harrington Ingham, a psychologist, drew the window with Joseph Luft, and its name is made from their first names. The panes, open, blind, hidden, and unknown, follow from crossing known or unknown to oneself with known or unknown to others. It is a teaching model for training groups and feedback, not a measured instrument, and it works best used that way.

How to run it

  1. Draw the four panes. Label them open, blind, hidden, and unknown, and say plainly what puts something in each.
  2. Write traits on cards. The person and the team each write habits, strengths, and concerns about the person, one per card.
  3. Sort by who knows what. A card both wrote is open; one only the team wrote is blind; one only the person wrote is hidden.
  4. Ask for the blind pane. The person asks for those cards to be read and explained, and only thanks people, without defending.
  5. Choose what to disclose. The person picks one or two hidden items that matter to the work, and shares them at a pace that feels safe.
  6. Name one change per moved card. For each card moved to open, agree what the person or the team will do differently.
  7. Revisit in a quarter. Sort again and see how the panes have moved, adding anything new work has brought out.

Where it goes wrong

Feedback arrives without permission. A session becomes an ambush, the blind pane is emptied in one sitting, and the person shuts down. Let the person ask, set the pace, and keep the first round to the work.

Disclosure is pushed. Pressure to share hidden items turns a safe exercise into an unsafe one. Hidden items move only when their owner chooses, and some should stay hidden.

The window is used once. The panes look different a week later and nothing follows. Tie every moved card to a specific change, and check it at the next team review.

When to use something else

  • Difficult Conversations. When one specific blind spot needs raising, and the conversation itself is the hard part.
  • Nonviolent Communication. When feedback needs a form that states what was seen and what is needed, without blame.
  • After-Action Review. When the team needs to learn from a piece of work, not from how it sees one person.

Where it sits in SOLVE eX

Go to the source

  • The Johari Window, a Graphic Model of Interpersonal Awareness, Proceedings of the Western Training Laboratory in Group Development, UCLA, 1955

Back to the catalog