Competency Overlap Confusion: When Multiple Competencies Describe the Same Skills

You're documenting a community engagement project where you analyzed data, communicated with stakeholders, and considered organizational factors. As you review the competency list, three or four statements seem to describe what you did. Which one is correct? Does your work demonstrate all of them? Can you use the same project for multiple competencies?

This confusion is universal among practicum students, and it stems from a fundamental truth about public health work: real-world practice integrates multiple skills simultaneously. The competency framework artificially separates interconnected abilities to make assessment possible, but that separation creates documentation challenges.

Understanding Why Overlap Exists

CEPH competencies were designed to comprehensively describe what public health professionals should be able to do. Complete coverage inevitably means some skills appear in multiple contexts. Communication, for example, underlies virtually every public health activity. Data analysis informs most decision-making. Systems thinking applies across all practice areas.

This overlap isn't a design flaw—it reflects reality. When you conduct a community health assessment, you simultaneously collect data, engage stakeholders, apply evidence-based methods, and consider social determinants. Expecting these activities to map cleanly to single competencies misunderstands both the framework and professional practice.

Identifying the Primary Emphasis

When competencies overlap, focus on primary emphasis. Each competency statement has a central focus, even when peripheral skills are also involved. Read the competency carefully and identify what it most directly describes.

Consider the difference between competencies involving communication with stakeholders versus those involving data analysis. Both might apply to a project where you presented epidemiological findings to a community advisory board. The communication competency emphasizes audience adaptation and message delivery. The data competency emphasizes analytical methods and interpretation. Your work likely demonstrates both, but which was the primary activity?

Ask yourself: "If I had to describe this work in one sentence, which skill would be the verb?" The answer often reveals which competency fits best. This kind of focused thinking also helps when you encounter the related challenge of distinguishing foundational versus concentration competencies.

Using Context to Differentiate

Your specific work context helps distinguish between similar competencies. Two students might complete similar projects but legitimately demonstrate different competencies based on contextual emphasis.

If your project focused on selecting which data sources to use and justifying your analytical approach, that emphasizes evidence-based methodology. If it focused on presenting complex data in accessible formats for community members, that emphasizes communication. Same data, different competency demonstrations based on where you invested primary effort.

When documenting, highlight the contextual elements that distinguish your work. Don't just describe what you did—explain why that activity most directly connects to your chosen competency rather than alternatives.

When Multiple Competencies Genuinely Apply

Sometimes a single project legitimately demonstrates multiple competencies. This is acceptable, even desirable—integrated skill application reflects sophisticated professional practice. However, you need strategy for how to document this appropriately.

If your program requires demonstrating specific competencies, check whether you can use one project for multiple competency narratives. Many programs allow this, as long as each narrative focuses on different aspects of the work. Your community health assessment might generate one narrative about data collection methods and another about stakeholder communication, each emphasizing different competency elements.

When writing multiple narratives about the same project, make each one distinct. Don't simply restate the same activities with different competency language pasted in. Instead, genuinely focus on different dimensions of your experience. What did you learn about data analysis? That's one narrative. What did you learn about communication? That's a separate narrative with different reflection.

Seeking Clarification When Needed

When overlap creates genuine uncertainty, seek guidance. Your academic advisor or practicum coordinator has likely addressed similar questions before. They can clarify program-specific expectations and help you choose among reasonable options.

Prepare for these conversations by identifying the specific competencies causing confusion and explaining why you see overlap. Bringing concrete examples of your work helps advisors give targeted guidance rather than general statements. This is also an opportunity to address the broader challenge of selecting your five competencies if the overlap is making that initial selection feel impossible.

Don't view asking for help as admitting failure. Navigating competency documentation is genuinely complex, and seeking clarification demonstrates professional judgment—knowing when to consult others is itself an important skill.

Making Confident Choices

Ultimately, you must make decisions about competency mapping even when overlap exists. Avoid paralysis by recognizing that multiple reasonable choices often exist. Your goal isn't identifying the one correct answer—it's making a defensible choice and documenting it well.

Once you choose a competency, commit to that framing in your documentation. Hesitant language undermines your narrative. Instead of writing "This work might demonstrate communication competency," write "This work demonstrates communication competency through..." Confidence comes from specificity, and specific examples make any reasonable competency choice convincing.

The same principle applies when writing your competency mapping section—committing fully to your chosen framing produces stronger writing than hedging across multiple options.

FAQ

Q: Is it better to demonstrate fewer competencies with strong evidence or more competencies with weaker evidence? A: Fewer competencies with strong, specific evidence is almost always better. Reviewers are more impressed by detailed narratives showing genuine skill development than by brief claims about many competencies. Check your program's minimum requirements and focus your strongest evidence on meeting those.

Q: What if my advisor and preceptor disagree about which competency my work demonstrates? A: This disagreement often reflects the legitimate overlap you are navigating. Ask both to explain their reasoning, then make a decision based on where your evidence is strongest. Your advisor's perspective on program expectations should carry particular weight since they understand the evaluation criteria.

Q: Can the same activity count for both a foundational and a concentration competency? A: In many programs, yes. A single project can demonstrate different competencies at different levels. The key is ensuring that each narrative focuses on distinct aspects of the work and that the evidence genuinely supports the competency claim at the appropriate level of specificity.

The competency framework guides professional development—it's not a rigid sorting system with only one correct answer for each activity. Trust your judgment, document thoroughly, and focus on demonstrating genuine skill development rather than perfect categorization.