One ERP Project, Three Executive Readers: How to Change the Emphasis Without Changing the Facts

You led a technology implementation with implications for operations, information, and organizational change. Now you are considering different executive roles. Should the accomplishment appear exactly the same way on every resume?

The facts should remain the same. The emphasis can change. In my 3 Executive Resume Strategies Live, I used this kind of project to show why the person reading the resume matters.

Start with a fixed set of facts

The Live’s illustrative ERP example involved unifying five disconnected business units on one platform, giving leaders real-time performance visibility, and reducing reporting time by 40%. These are teaching details from the session, not a client case study.

For this exercise, those are the available facts. We cannot add cost savings, cybersecurity improvements, adoption rates, or a change-management challenge simply because they would make one version stronger.

• Fix the project’s scope, ownership, action, and verified result.
• Do not add outcomes merely to strengthen a target-role version.

Use the same discipline with your own project. Establish the scope, your actual responsibility, the action, and the verified result before tailoring the language.

For a COO reader, foreground the operating value

In the Live, I described a COO’s possible interests in operations, productivity, cost, and visibility. The actual job description should determine which of those matters for the role you are pursuing.

Using only the example’s facts, an editorial version could read:

Reduced reporting time by 40% and improved real-time performance visibility by unifying five disconnected business units on one ERP platform.

• Lead with the operating result relevant to the role.
• Add cost savings only when your own evidence supports them.

This version brings the operational result forward. It does not claim cost savings because the example does not supply them. In your own resume, add the leadership verb that accurately describes your contribution rather than implying ownership you did not have.

For a CIO reader, foreground integration

The Live discussed technology integration, data governance, adoption, and cybersecurity as possible concerns for a CIO reader. That does not mean every technology project demonstrates all four.

A version limited to the example’s facts could read:

Unified five disconnected business units on one ERP platform, enabling real-time performance visibility and reducing reporting time by 40%.

• Bring integration or other relevant technology evidence forward.
• Keep unsupported security, governance, or adoption claims out.

The order emphasizes integration. There is no added claim about security, governance, or user adoption. If your own project includes supported evidence in those areas and the target role calls for it, you can select that evidence. If it does not, leave it out.

For a Chief Transformation Officer reader, examine the change evidence

The Live identified alignment, resistance, adoption, and change measures as relevant questions for a transformation reader. Our short example establishes consolidation across business units, but it does not tell us how people adopted the change.

We can foreground the cross-business transformation:

Brought five disconnected business units onto one ERP platform, creating shared real-time performance visibility and reducing reporting time by 40%.

Then we should ask for more evidence rather than invent it. What leadership alignment did you establish? What changed in the way the units worked? How was adoption demonstrated? Only supported answers belong in a fuller version.

• Foreground the verified change across business units.
• Develop further alignment or adoption claims only from supported evidence.

These three sentences are editorial adaptations of the Live’s example, not verbatim quotations. They illustrate changes in emphasis, not three different accomplishments.

Read the job description before choosing a version

Titles are a starting point, not a complete description of the hiring need. A particular COO role may focus on integration. A particular CIO role may prioritize operating efficiency. Select evidence for the stated problem rather than relying on a title alone.

• Use the actual hiring priorities, not the title alone.
• Choose the version that answers the stated business problem.

Our existing article on targeting a resume for a role or industry covers the broader principle. This exercise applies it to a single accomplishment.

Check that the versions still agree

Compare them side by side. The scope, numbers, dates, and your contribution should remain consistent. Reporting time must not turn into operating time. A team effort must not become sole ownership. An implementation must not acquire outcomes that were never measured.

• Compare scope, numbers, dates, and ownership across versions.
• Preserve the precise measure, including reporting time versus operating time.

Return to the executive resume evidence guide to place the selected example in the wider document. If you need help choosing and presenting the right evidence for your next role, contact our executive resume team.