Why is it hard to explain my part in a successful project?
In many jobs, outcomes are a team effort. That naturally makes it difficult to talk about the results of a project, especially when you are interviewing for a new role and someone wants to understand what you contributed. Even more so when the project is really big involving a bunch of people. Sometimes we feel like those results were going to happen whether we were there or not.
You know the project went well. You know you were involved. But how do you explain your part without taking credit for everyone else’s work?
And, we do have to be careful here, because a project’s results do not automatically tell us what any one person contributed.
Imagine telling an interviewer, “I helped drive a 30% increase in pipeline for a new product.”
They ask, “Great. What did you do, and how did that contribute to the increase?”
If your answer becomes a list of activities with no clear connection to that result, you may be claiming more than you can explain. And you’re setting yourself up to not make the next round pretty quickly.
So it’s fine for you to describe the team’s success. You just also need to be clear about what your contribution actually did.
What did I bring beyond completing my assigned tasks?
It is easy to approach work as a sequence of activities: someone tells you what needs doing, you complete the tasks, and you move to the next project.
Sometimes you learned a process once and have continued using it without examining why it works, when it needs to change, or whether another approach would suit the situation better. (This is another trap I talk about in your competency types.)
When I work with people on developing their craft, I want to get underneath that sequence.
Your craft is the approach you develop through your experience, perspective, and judgment. It shows up in how you uniquely do the work.
What did you notice? Why did you start where you did? Did you ask a question that changed the direction? Did a lesson from an earlier project influence a decision? Which of your strengths did you lean into? Which of your values did you tap?
Someone else might have completed the same tasks but approached them differently, involved different people, or done them in a different order.
Understanding those choices helps you explain your contribution. It also gives you something to develop as you take on more responsibility.
Then comes the next question:
What did your approach allow to happen?
Perhaps it helped another team make a decision, clarified a disagreement, or changed how the work was organized. Those effects matter even if the project might ultimately have reached the same headline result through a different route.
You do not have to prove that everything would have failed without you. You need to explain what you brought and what it enabled.
What is the CLEAR framework?
CLEAR is a framework I developed for writing career stories and understanding your contribution to the work.
I teach it within Innervates as part of discovering your craft, preparing for a promotion, and changing jobs. It helps connect what you did with how you think, what your approach made possible, and what you learned.
If you are familiar with STAR, you may recognize some similarities. I think STAR is useful, for sure. CLEAR is my way of giving additional attention to the contribution and reflection that I often find missing from career stories.
The letters stand for Context, Leverage, Emerged, Achieved, and Revealed.
Choose a project from the past six to twelve months, and think through each of the following letters.
C — Context: What was happening?
Give the reader or listener enough information to understand the project.
What was the team trying to accomplish? What problem were you addressing? What was your role?
Include details such as company size, team size, or whether you were an individual contributor or a manager when they help explain the work. A similar project can involve very different challenges and results in different settings.
Keep this part short. You are setting the scene so your contribution makes sense.
L — Leverage: What did you bring to the work?
This is your particular contribution: the perspective, experience, or way of thinking you brought into the project.
Perhaps you recognized a problem because you had encountered it before. Perhaps you questioned an assumption, approached the work in a different order, or connected information that had been considered separately.
We really want to go beyond naming a task, we want to explain how you approached it and why. If you’ve walked your career timeline or worked with a coach 1:1, this becomes a lot easier to write, because it will be grounded in patterns of strength your entire life.
What was present in the work because you were the person doing it?
This can, and usually does, take some deep reflection. The decisions that feel obvious to you may be precisely the parts you need to explain.
E — Emerged: What did your contribution enable?
Now connect your approach to what happened next.
Did it help another team move forward? Did it change the scope, clarify a decision, improve a handoff, or allow you to do your own work more effectively?
Leverage and Emerged are closely connected, but they answer different questions. One describes what you brought. The other describes what that then made possible.
For a hypothetical example, imagine you compared customer-interview notes with proposed launch messaging and noticed that two teams were describing different customer problems. You brought that disagreement into a discussion and helped the teams resolve it.
Your contribution was identifying and addressing the mismatch. What emerged was a shared understanding that the teams could use to develop their materials.
That is a much clearer explanation than simply saying, “I worked on refining messaging for the launch.”
A — Achieved: What was the ultimate result?
Describe the final accomplishment or outcome.
This is where a relevant metric can belong, provided you can support it and explain its relationship to the work. You can also describe a meaningful outcome without attaching a number.
Continuing the hypothetical example, the teams might have completed the launch with consistent messaging across their materials. That is a shared result. Your contribution helped make the alignment possible; other people still did the work of creating and delivering the launch. And you could tie it into a further metric (if it holds) that the consistent messaging allowed for stronger levels of engagement across multiple pieces of media.
Keep that connection clear! You can tell the larger story while still being accurate about your part in it.
R — Revealed: What did the project teach you?
This is the reflection that I think gets left out almost all of the time.
What did the project reveal about your approach? What did you learn about how you think or work? What would you repeat and what would you change?
If you faced a similar project six months from now at another company, what would you do differently because of this experience?
In the launch example, you might decide to check whether teams agree on the customer’s problem before anyone starts drafting materials. The experience has changed how you would approach the next project. That reflection is CRITICAL to the value your work provides a future employer. Your ability to describe that workflow based off learned experience, a story, and your unique way of approaching your career is what changes the game.
That is part of refining your craft: doing the work, examining what happened, and using what you learned to improve your approach.
Which parts of the story deserve the most attention?
When I reflect on my own interviews, listen to others, or coach someone through their career stories, Leverage, Emerged, and Revealed are the pieces I care about most. They are also usually the hardest ones that are almost always left out of interview answers, career highlights, and promotion packages.
Keep the context brief. Include the result, but give yourself room to explain your contribution, what it enabled, and what you learned.
As you write your story, look at where you have spent the most time. If most of it describes the project setup or celebrates the team’s result, return to those three parts.
What did you bring? What did that allow to happen? What did the experience change about how you work?
Those answers help someone understand your contribution within a team effort. They also help you recognize what you can carry forward and improve.
That learning can make your work more valuable to others in the future. But remember, your value as a person was never dependent on the project’s result.
