Why should executive support roles be designed from tasks?

Abstract

OPM calls job analysis the foundation for connecting work tasks to required competencies [1]. O*NET and BLS add occupation-level descriptions, requirements, and labor estimates [2][3][4][5]. Together, they support a two-layer role design: use public occupational evidence for the baseline, then document the employer’s actual service demands and dependencies.

Methodology

The analysis compares ten public sources covering job analysis, task collection, occupational requirements, assessment strategy, competency policy, and structured selection [1][2][3][4][5][6][7][8][9][10]. Because national sources and local workflow records use different denominators, they are not merged into a synthetic role score.

Layer one: establish the occupational baseline

O*NET and BLS organize executive secretaries and executive administrative assistants under occupation 43-6011 [2][4]. The sources describe common work but cannot capture every internal title. A chief-of-staff hybrid, personal-support assignment, or specialist role may only partly fit the public boundary.

Layer two: observe the local demand system

Record recurring outputs, request sources, timing, systems, physical presence, confidentiality, and backup dependencies. Separate normal demand from high-consequence exceptions such as board changes or urgent travel. This reveals whether the organization needs one broad role, a team, or explicit specialist escalation.

Translate tasks into entry requirements

OPM guidance connects job analysis with assessment and competency decisions [1][6][7]. Hiring teams should distinguish capabilities required on day one from terminology and context that onboarding can teach. Otherwise familiarity may displace stronger evidence of prioritization, written communication, and reliable execution.

Test the design against actual work

After hiring, compare the map with task frequency, unplanned work, authority exceptions, training gaps, and coverage failures. A rising share of unscoped work may indicate role drift rather than individual underperformance. Update the role when the operating model changes.

Where the public data stops

National occupational evidence does not decide a private employer’s classification, compensation, exemption, accommodation, or precise responsibility boundary [3][4][5]. Those questions need qualified local review. The useful output here is a dated task-and-dependency model, not a universal job description.

Key findings

  • Public occupation data provides a baseline, not a complete local role [2][3][4][5].
  • Local demand should be mapped by output, timing, authority, confidentiality, and backup.
  • Entry requirements should be separated from learnable organizational context [6][7].
  • Post-hire drift is evidence about role design as well as performance.
  • Legal classification and compensation decisions remain outside the cited data.

Sources

  1. Job Analysis, U.S. Office of Personnel Management
  2. Executive Secretaries and Executive Administrative Assistants: Details, O*NET OnLine
  3. O*NET Data Collection Program, O*NET Resource Center
  4. Executive Secretaries and Executive Administrative Assistants, U.S. Bureau of Labor Statistics
  5. Executive Secretaries and Executive Administrative Assistants Requirements, U.S. Bureau of Labor Statistics
  6. Designing an Assessment Strategy, U.S. Office of Personnel Management
  7. Competency Based Policy, U.S. Office of Personnel Management
  8. Structured Interviews, U.S. Office of Personnel Management
  9. Structured Interviews: Assessment Method Considerations, U.S. Office of Personnel Management
  10. Structured Interview Guide, U.S. Office of Personnel Management

Return to the Research Content library