Individuals and interactions over processes and tools.
The people of the organization are the most important thing, everything else is secondary.
The second highest priority is the delivery of quality healthcare to the community.
Providing good healthcare over profits, expansion, political jockeying, career advancement, or being progressive. Taking people to the hospital and being nice to them is 90% of the job.
Guidelines over strict regulations.
Protocols must be guidelines that allow people to accomplish the goal of quality patient care. Protocols should not be rigid doctrine that must be followed even if the results are deleterious.
Welcoming changing practices based on new evidence and knowledge.
Evidence kills sacred cows and dogma – walk away from things that no longer serve a purpose.
Build projects around motivated individuals.
This means hiring the right people – ones that you are willing to invest in over the long term. Build a team, not a workforce.
The most efficient and effective method of conveying information is face-to-face conversation.
You must talk with the providers in your system face to face – there is no substitute.
A sustainable work lifestyle.
You can’t successfully provide quality healthcare to a community by forcing people to work overtime for months at a time and burning them out.
Continuous attention to technical skills.
Skills must be practiced regularly or they will atrophy. Skills should not be the hard part of the job; thinking should be the hard part.
Simplicity – the art of maximizing the amount of work not done – is essential.
Get rid of the bullshit; in the documentation program and in anything else that prevents good patient care from happening. Simplify and streamline processes, remove things that suck the joy out of work.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Honest evaluations and feedback are needed at the individual and organizational level. When a measurement becomes a target, the value is lost.
Adapted and/or straight up plagiarized in parts from: https://www.agilealliance.org/agile101/12-principles-behind-the-agile-manifesto/
I am not one for manifestos. I don’t really like the word manifesto as it has taken on a meaning different than the actual definition, but it is what the original document was called when a small group of software developers that were fed up wrote the Agile Manifesto in 2001.
Make no mistakes here, this is idealistic, hell, maybe it is even unrealistic but it might be what is needed.
emsqaqi 