Are You a Program or Project Manager?

There are thousands of program managers / project managers in the federal government! If you are one of them (or want to be one of them), you should know about the Program Management Improvement Accountability Act (PMIAA). The PMIAA requires, in part, that most federal agencies designate a senior executive as their Program Management Improvement Officer (PMIO); in turn, the PMIO should implement a program for enhancing the role of program managers.

That program includes improved career paths and training.

The Office of Personnel Management (OPM) recently issued guidance that identified the key skills and competencies for program managers. The competencies were created based on focus groups that included more than 7,000 employees across government. These competencies are expected to form the frame for training and development of program and project managers going forward.

As an existing or aspirational program / project manager, think about your existing skills and experience in this framework; if you have gaps, and these competencies are relevant to your specific position, you may want to address any gaps through your Individual Development Plan (IDP).

I would also encourage you to think about these competencies as key words to be sure to include in your resume!

General Competencies

• Accountability
• Attention to Detail
• Conflict Management
• Creative Thinking
• Customer Service
• Decision Making
• External Awareness
• Flexibility
• Influencing/Negotiating
• Information Management
• Integrity/Honesty
• Interpersonal Skills
• Leadership
• Legal, Government and Jurisprudence
• Manages Human Resources
• Manages Resources
• Oral Communication
• Organizational Awareness
• Partnering
• Planning and Evaluating
• Political Savvy
• Problem Solving
• Reading Comprehension
• Reasoning
• Strategic Thinking
• Teaching Others
• Team Building
• Teamwork
• Technical Competence
• Technical Credibility
• Technology Application
• Writing

Technical Competencies

• Acquisition Strategy
• Business Process Reengineering
• Capital Planning and Investment Assessment
• Change Management
• Compliance
• Contracting/Procurement
• Cost-Benefit Analysis
• Financial Analysis
• Financial Management
• Knowledge Management
• Performance Measurement
• Program Management
• Project Management
• Quality Management
• Requirements Management
• Risk Management
• Schedule Management
• Scope Management
• Stakeholder Management

More information about the program and project management competencies can be found here: https://www.chcoc.gov/sites/default/files/PMIAA%20Competency%20Memorandum%20Attachment%20for%20CXO%20Councils.pdf.

Your Resume Should NOT Use the Word “I” … and other tricks of the trade—

I often receive feedback from clients about the resumes I have prepared for them; one of consistent comments I receive is about the word “I.” While resumes should not be written in third person (who likes the “royal we”?), they should not use the word “I” either. Resumes are appropriately written in first person implied. This means that not only should you not use “I,” you should not use other personal pronouns such as me, my, we, our, etc., either.

Read more

How to Write Accomplishments & Show Your Value

There are many people, sometimes 1,000 or more, applying for the same job. As an applicant, it is critical that you know how to differentiate yourself from others. There are lots of ways you can demonstrate your value—in a cover letter, in your resume, in your interview, and through your thank you note. No matter which way or ways you choose to show your value-add, the “how” is pretty consistent.

Follow these steps:

Track your achievements. Get in the habit of writing down (or using an electronic format) for your accomplishments throughout the year. Spend 5 minutes a week to make some notes. Not only will those notes be useful when you prepare your resume, they will be useful in writing your annual accomplishment report for your performance evaluation, preparing for interviews, etc. In that file, keep a copy of “kudos” received from customers, team members, and your boss, as well as awards and other recognition you have received.

Keep your numbers. In addition to tracking achievements, be sure to quantify those achievements. It’s one thing to say you saved money or increased productivity, using a number to describe the savings or productivity takes that achievements to a whole new level. When think about numbers, think: how many, how much, and how often.

Use strong language to describe your success.
There are lots of powerful verbs out there; use them! Some of the words you might use include:

  • Improved
  • Enhanced
  • Saved
  • Created
  • Developed
  • Reduced
  • Achieved
  • Identified

Think CCAR. CCAR (context, challenge, action, result) is a powerful way to frame your achievements and tell your story. CCAR can be used for resume accomplishments, as well as in your performance self-assessment and in interviews. Here is what it means:

Context.  Describe the individuals and groups you worked with, and/or the environment in which you worked, to address a particular challenge (e.g., complexity, co-workers, members of Congress, shrinking budget, low morale, impossibly short deadlines). Make sure this is at the executive level. Think about examples where you were the initiator of an idea that had enterprise-wide impact.

Challenge.  Describe a specific problem that needed to be solved. Remember to think as holistically as possible. Think about the large-scale project/problem, if you have suitable examples.

Action.  Discuss the specific actions YOU took to address a challenge. Use “I” not “we” even if you were part of a team.

Result.  Give specific examples of measures/outcomes that had some impact on the organization. These accomplishments demonstrate the quality and effectiveness of your work toward organizational goals. Metrics always help support your results. If your result was qualitative, how can you show it was substantial? Perhaps a quotation from an award recommendation or performance evaluation, or a comparison to a prior situation.

Here’s what it looks like in response to an interview question:

Context: “I work as an IT specialist at a small local government agency.  About a year after I started, the Director decided to update the agency’s website, my job was to test and launch the new website after it had been designed and developed.”

Challenge: “This was challenging because the website was 5 years old, used old technology, and no updates had been made since the original launch.  In addition, I was given only 2 weeks for testing and launching—there was a lot of pressure.”

Action: “I created a comprehensive testing strategy and schedule for reviewing all of the new website’s content and graphics.  I established daily check-ins with testers to ensure all timelines were met and all issues were identified and addressed.”

Result: “As a result of these efforts, I launched a new website within the timeframe allotted to update it.  Hits to the site have increased by 25% and our agency receives a lot of positive feedback on the new website. I have received requests from other local government agencies for advice on how they could update their sites.”

In an interview, using “I” is critical; if you were writing the above achievement for inclusion in your resume, it might look something like this:

In just 2 weeks [challenge], updated, tested, and launched a new website, overhauling a site [actions] that had not been updated in 5 years [challenge]. Hits to the site increased 25% within 90 days of launch [result].

Are You Ready to be a Government Leader?

The penultimate leadership opportunity in the career federal service is the Senior Executive Service (SES). While we all know people who are in the SES that perhaps shouldn’t be, ideally, the SES represents the best of the best the government has to offer.

Read more

Preparing Executive Core Qualifications (ECQ)

You’ve examined your qualifications and interest, and made the decision to apply for the Senior Executive Service (SES). It is time to start working on your ECQs. Don’t wait until you have a specific SES posting. There is absolutely no reason why you cannot work on your ECQs now.

Not Job Specific

ECQs are NOT job specific; instead, they are about your leadership. Getting your ECQs prepared ahead of time will allow you the necessary time to prepare your executive resume and any Technical Qualifications (TQ) associated with an individual posting. Once you have a strong set of ECQs, you can use them across multiple postings.

What goes into ECQs?

ECQs include specific evidence of your possession of the each of the 5 executive competencies (leading change, leading people, results driven, business acumen, and building coalitions). In addition to the 5 ECQs, there are also 28 sub-competencies embedded within the ECQs and an additional 6 cross-cutting competencies that should be clearly exhibited throughout your ECQ document.

What is CCAR and why does it matter?

CCAR (challenge, context, action, result) is the Office of Personnel Management (OPM) rubric that must be used for your ECQs. Using this rubric will help readers of your ECQs understand your stories. The CHALLENGE is the specific problem you faced, the CONTEXT tells the reader about the people involved, the organization, the larger climate, and other details that demonstrate the executive nature and complexity of the challenge. ACTIONS are the things that you personally did (or that you directed others to do) to address the challenge. And of course, RESULTS are proof that you solved the challenge. In a perfect world, results should be demonstrate using qualifiable metrics; it’s not enough to say “things improved…” you need to prove that they improved.

What are your ECQ stories?

Before starting to write, you should identify your ECQ stories. Your stories need to be executive (rather than transactional) and ideally show enterprise-wide impact. Examples should be from the past 10 years (5-7 years is better if possible). Your examples should have an ending so that you can demonstrate results. If your specific example has not yet fully concluded, provide a specific metric to demonstrate progress. And obtaining a degree or talking about your philosophy will not be considered executive. Focus on specific leadership achievements.

How can you identify your stories?

There are two ways to go about identifying your stories; the first way is to identify when you led change, led people, etc. The second way is to identify your most significant achievements from the past 10 years and then match them to a specific ECQ. Both ways work; you need to figure out what works bet for YOU. It is not unusual to have more stories than you need for Results Driven and not enough for another ECQ. If that is a situation you face, review the underlying competencies for the ECQs and see if you can tell your story in that frame. For example, if you have too many Results Driven stories and not enough Leading Change, look at the underlying competencies for leading change (vision, strategic thinking, innovation/creativity, external awareness, flexibility, and resilience) and see if you can think about how to tell one of the results driven stories through the leading change lens.

Other things to keep in mind:

Review OPM Guidance on preparing ECQs (see: https://www.opm.gov/policy-data-oversight/senior-executive-service/reference-materials/guidetosesquals_2012.pdf.) Try to have at least one action for each underlying competency in every ECQ (and keep the underlying competencies in the right ECQ). Use as many numbers as possible throughout your ECQs—numbers of people, dollar value of budgets / projects / contracts, timeframes, etc.

These numbers provide context to your stories and the ultimate readers of your ECQs is the Qualifications Review Board (QRB) at OPM—they will not know your agency or your job. Focus on your leadership, not your technical acumen. Be prepared to spend the necessary time to put together a good package; in my view, this is 40-60 hours.

And if you’re struggling with your package, get help! No one does this alone.