PEI / FIT INTERVIEW
You are preparing leadership stories for consulting interviews.
Your strongest recent example is a Master’s group project.
Then doubt arrives.
Does that even count?
Everyone does group projects.
Exactly. Which means the project itself will not make the story strong.
What happened inside it might.
“I coordinated the team” sounds useful... until everyone says it
You scheduled meetings.
Assigned tasks.
Made a shared document.
Tracked deadlines.
Helpful.
But if that is the entire story, the interviewer still knows very little about your leadership.
Leadership becomes visible when coordination stops being enough.
Someone disagrees.
The work is slipping.
The client changes the scope.
Two analyses point in different directions.
A teammate is not contributing.
The group is about to present something you think is wrong.
Now your choices matter.
Leadership needs resistance.
Without it, the story can sound like administration.
The best group-project story may begin when you lose control
Suppose your capstone team planned to recommend Market A.
Two days before the presentation, new data suggests Market B may be stronger.
Half the group wants to stay with the original answer because the deck is nearly finished.
You think the recommendation should change.
Now there is a real leadership problem.
Do you force your view?
Reopen the analysis?
Ask the team to define what evidence would justify switching?
Split the work?
Speak with the project sponsor?
Your actions reveal far more than the project title.
For examples of how strong and weak teamwork answers differ, read Teamwork Story Guide with Strong and Weak Versions.
Watch the word “we”... it can erase you completely
“We realized the analysis was wrong.”
“We changed the recommendation.”
“We finished the deck.”
All plausible.
But what did you actually do?
The interviewer is evaluating your behavior.
Try making the sequence visible:
“I noticed...”
“I proposed...”
“I spoke with...”
“I changed my approach when...”
“I persuaded the team by...”
“I took responsibility for...”
This does not mean stealing credit.
It means separating the team's outcome from your contribution.
Give the team the result. Give yourself the actions you actually took.
You do not need the title of leader... that may make the story stronger
Perhaps nobody appointed you.
You were one of four students.
That can make the influence more interesting.
You had to persuade rather than instruct.
You had to earn agreement.
You had to read the room.
You had to adapt.
Those are useful consulting behaviors.
Client teams contain people you do not manage.
Stakeholders may disagree with your recommendation.
Your authority can be limited.
So leadership without formal power is not a weaker story by default.
For examples of what consulting-style leadership can look like, read Leadership Story Guide with Three Consulting Examples.
One question decides whether your group project is worth using...
If you disappeared from the story, what would have happened differently?
If the answer is “not much,” find another example.
If the team would have remained stuck, chosen a weaker direction, missed the deadline, failed to resolve a conflict, or struggled to align, keep digging.
That difference is where your leadership lives.
Your story is not:
“We completed a successful group project.”
It is:
“The team reached a difficult moment, I did something specific, and the direction changed.”
That is much closer to what the interviewer is listening for.
And suddenly the fact that it happened in a classroom matters a lot less.