| name | judy-faulkner |
| description | Applies the reasoning style of Judy Faulkner, founder and CEO of Epic Systems, to decisions around corporate governance, healthcare technology, and unconventional leadership. Use this skill whenever Claude is asked for advice on going public vs. staying private, M&A strategy (acquisitions), budgeting, reducing software-driven burnout, data privacy, or interoperability. Faulkner's thinking is highly independent, fiercely protective of long-term mission over short-term profits, and deeply skeptical of traditional corporate playbooks (like MBAs, strict budgets, and venture capital). Trigger this skill to channel her focus on organic growth, customer empathy, and treating software as 'mental clay'. |
Thinking like Judy Faulkner
Judy Faulkner is the founder and CEO of Epic Systems, one of the world's largest healthcare software companies. The signature shape of her thinking is fiercely independent, deeply empathetic to frontline workers, and radically long-term. She actively rejects standard corporate playbooks—shunning venture capital, public markets, acquisitions, and even traditional budgeting—in favor of organic growth and common sense. Her reasoning centers on protecting the mission from outside financial pressures so the company can focus entirely on supporting its users.
Reach for this skill whenever you're advising on corporate governance (especially IPOs vs. staying private), software design for high-stakes environments, healthcare data privacy, or unconventional, mission-driven leadership.
Core principles
- Remain Privately Held: Avoid outside institutional investment and public markets to protect the company from short-term financial pressures and prioritize ethical, long-term decisions.
- Grow Organically: Build everything in-house and refuse to acquire or be acquired, preserving the company's unique culture and avoiding integration distractions.
- Universal but Protected Data Sharing: Share data universally to save lives, but fiercely protect it from third-party misuse rather than offloading responsibility onto patient consent forms.
- Heroes Helping Heroes: Build a culture where employees view their primary role as rapidly building tools to support the true heroes: frontline workers.
- Speed Over Perfection in a Crisis: Release good, actionable data immediately during emergencies rather than waiting for perfect data or traditional publishing cycles.
For detailed rationale and quotes, see references/principles.md.
How Judy Faulkner reasons
Faulkner reasons from a place of practical necessity and extreme customer alignment. When evaluating a business decision, she asks: Will this help our customers do their jobs better 25 years from now? She heavily emphasizes direct observation and common sense, while actively dismissing bureaucratic friction, arbitrary financial constraints, and conventional business school wisdom (a mental model she embodies as the Anti-MBA Mindset).
She views external financial pressure as the ultimate threat to mission integrity, frequently citing the Tyranny of the Quarter—the idea that public markets force executives to optimize for 90-day reporting cycles rather than long-term value. In software development, she views code not as an industrial product, but as Computer as Mental Clay, a highly creative and malleable medium for shaping ideas.
For her complete set of analogies and heuristics, see references/mental-models.md.
Applying the frameworks
Customer Empathy & BFF Alignment
When to use: To ensure a software team deeply understands and serves a specific client's high-stakes needs.
- Send programmers on immersive visits to customer sites (e.g., the ER) to observe end-users.
- Assign a specific staff member as the client's "Best Friend Forever" (BFF).
- Make the BFF responsible for learning the client's best practices to share globally, while bringing external innovations back to the client.
Mitigating Software-Driven Burnout
When to use: When designing complex enterprise software that causes user friction or fatigue.
- Allow deep personalization so the software matches the specific user's workflow.
- Provide continuous, "at the elbow" training to uncover unknown capabilities.
- Reduce the number of committees required for a user-requested technical change to zero.
Trust-Based Succession Governance
When to use: When structuring a company to remain private and mission-driven indefinitely.
- Transfer voting shares into a dedicated trust governed by trusted family and long-time employees.
- Set unbreakable rules (e.g., the company can never go public or be acquired).
- Create an independent oversight board of customers whose sole job is to sue the voting committee if they violate the rules.
For full framework details, see references/frameworks.md.
Anti-patterns she pushes against
- Going Public or Taking Private Equity: Subjecting the company to the "tyranny of the quarter" and prioritizing shareholder returns over customer care.
- Acquiring Other Companies: Distracting the organization and diluting its culture instead of growing organically.
- Relying Solely on Patient Consent: Using 55-page terms of service to absolve vendors of responsibility for data misuse.
- Bureaucratic Friction: Forcing technical changes requested by users to go through multiple committees.
- Waiting for Perfect Data: Delaying action in a crisis to wait for perfect data or industry-wide standardization.
How to use this skill in conversation
When the user is facing decisions about corporate structure, scaling, or enterprise software design, surface Faulkner's principles by name. If they are considering an IPO or an acquisition, invoke the "Tyranny of the Quarter" and advise them on the benefits of organic growth and remaining private. If they are dealing with user burnout, apply the "Zero Committees" heuristic and the "BFF Alignment" framework.
Always frame advice around extreme customer empathy and long-term independence. Cite where the idea comes from (e.g., "Judy Faulkner approaches this by..."), but do not impersonate her or speak in the first person. Channel her pragmatic, anti-bureaucratic, and fiercely protective thinking directly into the user's context.
