Skip to main content
This page documents where Roy is effective, where he’s not, and why.

Optimal Conditions

ConditionWhy it worksExample
Clear goal, autonomous pathRoy needs to understand what success looks like. He doesn’t need instructions on how to get there.Chia Network: “Build developer education for a new language.” No playbook. Roy designed the curriculum, coached the engineers, built the system.
Competent leadershipStrong leadership means Roy amplifies what’s working instead of fighting dysfunction.Precision Nutrition: Built security improvements on a solid foundation with a competent CSO.
Problems worth solvingDocumentation that helps people find things. Training that changes behavior. Process improvements that remove friction.All roles: Roy’s best work comes from problems where the outcome is better systems and clearer thinking.
Remote or flexibleRoy has worked remotely since 2018. He’s already solved the coordination problems most distributed teams struggle with.Built systems, trained employees, and coordinated cross-functional work across time zones at every role since 2018.
Protected focus timeDeep work produces Roy’s best output. Autonomy and minimal unnecessary meetings let his strengths show up.Every role since 2018 has been remote with self-directed scheduling.

Constraints

ConditionWhat happens
Persistent ambiguity, no resolution path”We’re figuring it out” is fine. “We don’t know what we want and won’t decide” is not. Roy can handle uncertainty in problem-solving. He can’t fix organizational dysfunction from a non-leadership position.
Absent or indecisive leadershipRoy needs leadership that articulates vision, makes decisions, and removes blockers. Not micromanagement. Direction.
Performative workCompliance exercises that don’t improve security. Documentation no one reads. Processes that exist because “that’s how we’ve always done it.” Roy will do it if required. It’s draining.
Motivational leadership expectedRoy clarifies, stabilizes, and helps people think. He doesn’t pump people up. If the role needs a cheerleader, Roy is the wrong hire.
Speed over correctness as defaultRoy moves fast when the path is clear. He struggles when speed is permanently prioritized over thinking through consequences. This is different from emergencies; Roy is calm and effective in actual crises.

Active Development

Areas Roy is currently building:
AreaGoal
Technical depthDeeper expertise in AI/LLM applications, documentation systems architecture, and instructional design. Not to specialize, but to make better design decisions.
Influence without authorityLeading through competence across teams where he has no direct control. Managing up effectively.
Reducing initial resistanceRoy’s directness sometimes creates friction before people realize he’s right. Working on strategic packaging without reducing clarity.

Fit and Friction

Role typeComfortable withNot comfortable with
SalesTechnical pre-sales, solution architecture, customer educationCold outreach, quota-driven work, networking for networking’s sake
Political environmentsManaging up, stakeholder alignment, strategic communicationEnvironments where impression management matters more than delivery
Constant context-switchingShort bursts when neededAs a primary work mode
Conformity-driven cultureAdapting communication to audiencePerforming personality to fit organizational norms

Hiring Decision Summary

Roy is most valuable when you need:
  • Clear thinking on hard problems
  • Systems that work without constant maintenance
  • Knowledge captured and transferred effectively
  • Calm presence during uncertainty
  • Honest assessment over reassuring narrative
Roy is least valuable when you need:
  • Motivational energy as the primary contribution
  • Tolerance for persistent organizational dysfunction
  • Impression management over delivery
  • Perpetual urgency with no room for judgment
See also: Behavioral Competencies, Case Studies