When dividing project work, decide three things first: what evidence the task requires, who has the interest and time, and what result you’ll review in two weeks. MBTI can give people language for communication preferences if they choose to share. Assign work using deliverables, demonstrated skills, and project constraints. Anyone who skips the test or keeps the result private can still volunteer to lead, pair up, or rotate under the same criteria.
Copy these three lines for your kickoff.
Task: What do we need to deliver, who checks it, and what access do we need?
Person: Would you like to lead, try it with a partner, or revisit the timing? What relevant work can you show?
Review: When will we look at a sample? What would trigger extra help, rescheduling, or a new owner?
Write down the task before asking how people work
“She seems like an I, so give the demo to someone else” and “He’s a J, so give him the schedule” both skip the facts you need. A client demo means explaining key steps, handling uncertain questions, and confirming what you’re authorized to show or promise. Scheduling means checking dependencies, finding the decision-maker, and notifying affected people if there’s a delay. A willingness to speak publicly or a tidy desk doesn’t establish those skills.
The Myers & Briggs Foundation distinguishes preferences from skills, abilities, and competence. Its ethics code says taking the instrument is voluntary, people decide whether to share results, and results should not be used to screen job applicants. At a kickoff, ask what helps people take in information, what conditions they need to deliver, and what they’d like to try. Check access, available time, and existing commitments. You can hold that conversation without sharing any test results. Foundation guidance for organizations · MBTI Code of Ethics
A facilitator might open with: “We’re deciding who does what and what support they’ll need. Test results are private unless you choose to share. Tell us what information, prep time, or review would help.” Keep notes about the work, owner, due date, communication needs, and review. Even if someone shares four letters, record a useful request such as “Send the questions ahead of time.” Don’t forward a screenshot of their report to people joining later.
How would you divide work for a customer pilot?
Fictional example. A five-person team has two weeks to deliver a revised guide, a customer demo, and an issue log. The customer can only access the demo environment. The project owner approves any promise about additional access or delivery dates. Each deliverable could have one owner or a lead and partner. Decide who will review it before making assignments.
| Task | Evidence to consider | What the person chooses |
|---|---|---|
| Explain the workflow and answer customer questions | Use the same practice prompt to check whether the presenter explains the steps, flags unknowns, and confirms a follow-up time. | Luo Ke describes herself as leaning toward I and volunteers to present. She’ll run a ten-minute rehearsal with questions. |
| Log issues and follow through | Turn two live questions into records with evidence, an owner, and a deadline. | Cheng Yu has relevant examples and volunteers to pair. Send the meeting notes to the customer for confirmation; keep unverified points internal. |
| Revise the user guide | Use the same editing exercise and have the reviewer check steps and changes. | Zhou Ning has written similar guides and volunteers to lead. The project owner arranges environment access. No weekend deployment is planned. |
Luo Ke wants questions in advance. Cheng Yu prefers talking through who owns an issue. Send the outline one day ahead, allow spoken clarification during the demo, and use the issue log afterward. Both approaches are available to the whole team. If Luo Ke doesn’t want to present next time, record that decision without reinterpreting her type.
Suppose another person is great at live communication and wants to present but can’t rehearse because of a higher-priority commitment. Offer a short rehearsal segment, the chance to share sample questions, or a turn next time. That preserves a path to participate without treating skill as a commitment. For restricted work involving compliance, customer data, or production access, put an authorized and qualified person in charge first. Use controlled practice to build evidence for others.
What can you ask when someone assigns work by type?
Turn the label into a question the person can answer. Ask them directly when possible.
| What comes up in the meeting | What to ask instead |
|---|---|
| “You’re an E. You’ll be great with customers.” | “The demo has ten minutes of explanation and five of questions. Which part would you try? What prep would help?” |
| “You’re an I. Work behind the scenes.” | “Would you try facilitating, presenting, or taking notes? We can rehearse under the same conditions.” |
| “You’re an F. You should calm the customer down.” | “We need to explain a change, confirm the impact, and set a reply time. Who’s handled that before, and who wants to pair up?” |
| “You’re a P. The schedule will slip.” | “What are the dependencies? When can we confirm the materials? Who needs the first update if there’s a delay?” |
Let people choose whether to discuss a result. If someone asks you to stop mentioning it, return to access, time, and work samples. If the same person always presents, ask whether they want to present again or rotate. For permission and privacy examples, see how to talk about someone else’s personality results. That article uses the Big Five; the relevant practices here are asking first and discussing current behavior.
What should change after the two-week review?
For each deliverable, bring something the team can open and answer three questions: Was it delivered? Where did it get stuck? What do we change next time? Use a customer-checked issue log, demo notes, or a reviewed guide. A timely submission that leaves the next owner guessing what needs confirmation still needs better handoff criteria. A demo can happen on time while a key part is missing. Check access, materials, and rehearsal before assigning a cause.
In the fictional pilot, one action was skipped because the demo account lacked access. Record the skipped step, who checks access, and when to retest. Next time, check access before rehearsal. If someone else wants to try presenting, give them a lower-risk opening and let an experienced colleague handle difficult questions. Use a demo environment to verify unfamiliar requirements before expanding scope.
Compare the same person under different conditions. If edits were late, check for conflicting feedback from different reviewers. Have one reviewer consolidate requirements next time and record both the delivery and feedback windows. If materials, responsibilities, and practice were in place and a critical step still couldn’t be done, try pairing or temporarily changing the owner. Record the specific skill or support needed and assess progress against the task.
Amy Edmondson’s study of team psychological safety (PDF) found an association with learning behavior in 51 teams at one manufacturing company. For your review, one useful practice is making it possible to ask questions and admit omissions. This workflow is fictional. The study didn’t test this process or compare MBTI combinations.
What if someone declines the assessment, or two people want the same role?
Continue assigning work and ask everyone about relevant experience, current availability, and preferred roles. Make options like a kickoff outline, written confirmation for risky decisions, and private questions available to all. For a related approach to voluntary discussion and reviewing the outcome, see how teams can use Big Five language.
People who want to explore their preferences privately can choose the FermatMind MBTI personality test. Sharing is up to them. Assignments and performance reviews use the criteria agreed for the work.
If two people want to lead, give them the same material, access, and practice time for a short sample, and share the criteria first. If both qualify, split the work across two sessions, rotate the lead, or choose for this round based on project risk and availability. Review support after two weeks and decide what to change. Using work people can review and revise gives everyone a chance to influence the next assignment.


