1. Do not go public.
2. Do not be acquired.
3. Expectations = reality.
4. Keep commitments.
5. Be frugal.
6. Have standards. Don't do deals.
7. Create innovative and helpful products.
8. Have fun with customers.
9. Follow processes. Find root causes. Fix processes.
10. Don't take on debt for operations, no matter how good the deal.
11. Focus on competency. Do not tolerate mediocrity.
12. Teach philosophy and culture.
13. If you disagree, dissent. Once decided, support.
"Follow processes. Find root causes. Fix processes."
This one has always bothered me from a semantics angle. What is the Epic Employee to do with the knowledge of the Root Cause? Why was the employee told to find it? What if the process wasn't the root cause of the problem? I would have rephrased it to "Follow processes. Find root causes of problems. Fix root causes."
Epic has a lot of processes that need fixing, and since several of these processes have been flawed for the better part of a decade (at least), it's clear that Epic has no interest in fixing them. The most obvious example of this is their HR practice. Epic follows the practice of hiring the best and the brightest of the inexperienced. Shortly after the employee becomes competent with solo work, the load gets bigger until the employee either buckles under the strain or decides that the strain isn't worth it. At that point, the employee starts looking for work outside of Epic, taking all that experience with him.
The root cause of that problem is firing the employee instead of investing in their growth. Since Judy has gone on record at a staff meeting to lament their employee retention numbers, she could kill two problems by fixing one root cause.
Then there's the problem of Epic's development. Everyone who's gotten a peek behind the curtains knows that Epic's code base is held together with chewing gum and baling wire. A bona fide Patient Safety Escalation comes out every other week, and there are about a dozen Care Concerns each week.
Development processes were followed; Epic has numerous checklists for that. Problems were introduced into the product. Root causes were discovered by the Patient Safety committee. The problems were fixed after the fact (mostly), but the processes that allowed those issues into the software weren't modified.
The root cause of a given PSE is relatively easy to discover, and the code change required to prevent that specific problem from occurring in the future is manageable. However, the root cause of Patient Safety issues in general hasn't been looked at. How can Epic prevent buggy software from going out? I've heard suggestions (and posited some of my own), but nothing has changed.
While Epic talks a big game about fixing processes, they don't really deliver on that.