Skip to main content

A data driven resume to nail that next role.



The current project is coming to an end, and with it your contract, or possibly it’s time for another challenge elsewhere. Regardless of the reason it’s time to refine the resume to nail that next role. So what is required to standout from all those competitors, it is hard to come by important decisions that are made in the absence of data to support them. Managers are, understandably, loath to not have evidence stacked up to support a claim or decision that exposes their organization to opportunity, but also risk. 
This same perspective can be applied to hiring decisions as well. Are not employees a huge opportunity, albeit potential risk, for any business? A star employee can transform an organization for the better, resulting in a strong bottom line and happier customers. In a competitive job market, candidates need to sell their attributes and accomplishments to hiring managers, who increasingly need to base their hiring decisions on strong evidence, not unlike other operational or project decisions.
The resume needs to be quantitative, most resumes list work experience and education in a neat table, sorted by date and organization. This is a good start. However, when drilled down into the details underlying each previous job, the descriptions often leave something to be desired. For example;
·         “Compiled project analysis for company executives”
·         “Managed an organization-wide ERP solution implementation”
·         “Trained support teams on use of new software tool”
What these examples demonstrate is a lack of volume, scale, or size. How is a hiring manager to know if you managed the roll out of an ERP system for a staff of 10, or 2000? What does improved service delivery really mean? That each agent more consistently said thank you at the end of each call? Or were turnaround times reduced by 30%? Look for the ‘wins’ and highlight them with data.
Which can look like;
·         “Comprehensively analysed and compiled dozens of address, routing, and fuel data points on a weekly cadence, to draft executive reports that could be quickly understood and acted upon”
·         “Managed a 1 year ERP implementation affecting 900 staff, resulting in time savings of 5 FTEs”
·         “Facilitated dozens of training sessions of 525 participants each, achieving an average instructor rating of 4.5/5 from feedback forms”
The descriptions above provide a potential employer with the following takeaway.
·         $’s spent, saved or earned
·         Time taken or time saved
·         Cadence or turnaround time of process or task
·         # of people impacted, trained or involved
·         # of computers/machines updated or provisioned
·         Volume or quantity of materials 
What if the numbers aren’t impressive, when providing feedback on resumes, mentees often state they don’t think their accomplishments sound big or important enough if too much detail is given, as if keeping it vague somehow augments their work. If you don’t think an accomplishment is worth quantifying, remember that hiring managers can also revert to the lowest common denominator, if quantities aren’t provided. You may have concurrently managed 10 accounts worth an average of $10,000. In the absence of concrete numbers, a hiring manager may theoretically guess that maybe it was 4 accounts worth $5000 each. 
Sometimes, exploring different ways of telling your data story can make your work history sound more effective too. Maybe you successfully negotiated a $100 savings on a monthly vendor contract. That’s great, but maybe you can re-word it as, “Negotiated a 10% savings on a recurring monthly expense, saving $1000s per year”. Explore absolute versus percent versus ratio metrics for each claim, as sometimes one will sound better than the other. 
You may notice 2 distinct metrics types, often, when we are stuck in the weeds of our projects, we only think of our internal metrics. These could include things like # of stakeholders managed, dollars spent, or groups involved. What are often more impactful, in terms of convincing employers of the significance of your work, are metrics that speak to what your project ultimately accomplished; the downstream outcomes. Sometimes, these data points may not be known for months or years. These could include things like # of new clients, # of people trained, or incremental dollars earned or saved, directly due to actions you took while deep in the weeds of your project. Have a think about your last few projects. What were their downstream outcomes?
People differ on the utility of a personal interests or extracurricular section of your resume. Hiring managers, like all humans, are subject to nervousness around meeting new people in a formal interview setting. The personal interests section provide great small chat talking points to fill otherwise awkward pauses that can occur before and after the formal questioning part of an interview.
Just like with the other sections of your resume, be specific, and quantified, with your personal life! Instead of; 
·         “Organizer of musical festivals”, or 
·         “Love traveling and photography”
May look something like;
·         “Have organized 3 musical festivals with 1000s of participants each”, or
·         “Have traveled in 23 countries, and photographed the Taj Mahal to the fish & corals of the Great Barrier Reef”
Lastly, quantifying your resume is an exercise to perform not only once you are looking for your next contract or job, but on an ongoing basis, so that you can leverage the metrics you have formulated for yourself in conversations and informal networking chats.
Good luck on your next application!

Comments

Popular posts from this blog

Revisiting Managing Stakeholders, how to Nurture and thrive the relationship.

  Stakeholders can make or break projects, in order to ensure project success, effective stakeholder management is required. Identifying key stakeholders, dealing with difficult ones and creating a management plan can be overwhelming if you don't know where to start. Building positive relationships with stakeholders and proactively meeting their expectations can make the life of a project manager much, much easier.

How to Resource Plan

When managing a project or a project portfolio, it’s critical that resources and workload for each are intelligently distributed. Without proper resource allocation, projects can quickly get out of control in terms of expense and duration. With the right resource planning techniques, effective planning and management of resources in any industry can set you up for success. But before the break down on how Projectmanagementcompanion.com provides the perfect tools for resource planning and management, there must be a firm understanding on what resource planning is and how to compose a resource plan. Resource planning is one of the steps required when writing a business plan where all the resources in a proposed project are identified. This is achieved by creating a summary for managing workload that is comprehensive enough to make sure all the resources that are needed to complete the project are clearly identified. This summary is going to help get a buy-in from the sponsor an...

The difference between a Project Manager and a Scrum Master

By the nature of the work that Project Managers and Scrum Masters do, the two are not particularly closely aligned, even if it seems at first glance that they are. Managing a project is not the same as being a Scrum Master. Scrum Masters have the role of mentoring, teaching, coaching and facilitating, while the role of the Project Manager is to ensure that the project runs to time and budget. This means that the Scrum Master relies on more of the so-called “soft skills” involved with helping people to move forward, while the Project Manager takes a more methodical, and arguably more of a “hard skills” approach. While both roles have an interest in ensuring a high level of team performance and driving efficiency within the team, the ways in which they go about this are very different. The Scrum Master facilitates and coaches, while the Project Manager assesses risk and manages issues and conflicts.  Looking closer at what Project Managers and Scrum Masters do in terms of ...