Skip to main content
Three strengths define how Roy operates. They were identified through structured peer feedback from seven people across personal and professional contexts. See Core Strengths Methodology for process details and raw data. These three reinforce each other: staying calm enables clear analysis. Clear analysis produces better system design. Better systems reduce chaos, which makes it easier to stay calm. Roy is most valuable when problems are unclear, systems are broken, or people need to think instead of react.

Rapid Domain Acquisition

Roy learns whatever the problem requires. He moves between unrelated domains without starting from scratch.
“I do what must be done, and if I don’t know how, I learn.”

Evidence

ContextDomain learnedOutput
Chia NetworkBlockchain architecture, ChialispRewrote and reorganized existing community documentation as a volunteer; the CEO noticed and offered him a job
Precision NutritionWordPress architecture, knowledge managementEnterprise knowledge base for 200 employees
Singularity UniversityAI, robotics, biotech, digital manufacturing40+ executive workshops, IoT curriculum for 500+ participants
None of these were pre-existing skills. Each was acquired to solve the problem at hand.

Effect on others

Roy helps people separate what they know from what they assume. He does this through questions, not answers. People solve their own problems better after working with him. See also: Developer Education case study

Design and Systems Thinking

Roy designs for humans, not idealized users. He cares about efficiency and simplicity, and whether the design actually works for the people using it.

Evidence

Chia Network: Documentation was spread across a GitHub wiki, a Docusaurus site, and a 20,000-member Keybase chat. No style guide, no governance, no editor. Users kept asking the same questions because they couldn’t find or trust existing content. As a community member, Roy rewrote and reorganized the existing documentation. The CEO noticed and offered him a job. As an employee, Roy built contribution workflows, documentation standards, and governance processes to keep that quality consistent. Precision Nutrition: Internal knowledge was scattered across Google Docs and Slack. Roy built a centralized knowledge base with taxonomy, templates, and governance. Support requests dropped 20%. Chia Network (website): Rebuilt chia.net from 45 to 24 pages. Lighthouse performance improved from mid-80s to mid-90s. Designed backend framework to allow non-technical staff to update site without developer support.

Effect on others

Roy leaves systems in better shape than he found them. He’ll advocate for a better approach when he sees one, but the goal is always the work, not the argument. See also: Case Studies

Interpersonal Presence

Roy stays calm when others may panic. He shows care through competence, not sentiment. Peers describe him as having “gentle good humor” and being “a presence that is always around, and helps when help is needed.”

Evidence

Cybersecurity training (Chia Network): Designed curriculum around threat models and behavior change instead of fear or policy memorization. Treated employees as capable adults. Result: 90%+ completion, 100% pass rate across 75 employees. SME coaching (Chia Network): Coached 4 engineers with no presentation experience on speaking presence, pacing, and accessible language. Produced 9-part video series (46k+ views). Those skills stuck. Stakeholder management (Chia Network): Translated the COO’s ambiguous requirements into usable marketing assets by asking the right questions. Then taught him basic Figma so he could make text changes independently rather than depending on Roy across time zones.

Effect on others

When Roy is calm under pressure, other people can think instead of react. Trust comes from follow-through, not reassurance. One colleague: “I have a few people I know I can trust. You’re one of them.” See also: Enterprise Security Training case study, Behavioral Stories

Context Sensitivity

These strengths are context-dependent. Roy amplifies good environments. Bad environments constrain him.
Works wellDoesn’t work
Clear vision with autonomy to executePersistent ambiguity without resolution path
Competent leadershipAbsent or indecisive leadership
Problems worth solvingPerformative or checkbox work
Deep work with protected focus timeConstant context-switching as default mode
For a full breakdown, see Where Roy Fits.