Radical Results: A Security Org's Version of Radical Candor
summary
Repurposes Radical Candor into a team-level quadrant with axes vibes vs effectiveness and a plotted-dot tool (ejcx.dev/radicalresults) to score projects. Claims security teams should optimize for speed and more dots rather than perfect launches. Gives two concrete failures: a company-wide WebAuthn rollout that drags six months but could have shipped in a week, and a Linux device compliance effort stalled by endless focus groups that damaged relationships. Argues vibes materially change ability to manage risk.
AI-written summary · about
chapters (9)
- 0:00Introduction and welcome
- 1:29Talk overview and setup
- 3:56Recap of Radical Candor
- 10:35Applying framework to security teams
- 14:24Introducing the vibes axis
- 16:52Effectiveness as the second axis
- 18:39Tooling and real-life examples
- 25:20Conclusion and takeaways
- 27:06Q&A session
related talks
43mSecurity Kaizen for developers
21mRadical Therapy for Software Teams
24mRadical Transparency: Leading Engineering With Openness
39mProactive Security, less buzzword, more action
53mThe Psychology of DevSecOps
33mRapid-Fire Stories of Creative Solutions to InfoSec Problems
52mLeveraging Psychological Needs For Building A Security Culture Amongst Developers
46mIn Search of Security Shangri-la