Want to reduce the possibility of making errors when managing a database?
Hear Pythian founder Paul Vallee give an overview of Pythian’s FIT-ACER checklist and see how it helped Pythian reduce error rates from 1/year of services delivered to 1/ 6.3 years of services delivered.
To get your hands on some FIT-ACER checklists, visit https://www.pythian.com/fit-acer/
Want to talk with an expert? Schedule a call with our team to get the conversation started.
I just joined the Pythian team about 2 months ago and was introduced to the FIT-ACER concept during my on-boarding. When I first heard Paul’s pitch for FIT-ACER in my first few days there, I thought, “Yeah, it makes sense, but it’s like most checks: Great talk, great idea, but everyone just continues to go about their business.”
I was surprised to then see that it’s not just a “pitch”, but it’s actually ingrained into the complete culture. It’s prominently displayed on our computers, it’s on the walls, it’s even front-page on our ticketing system – front-and-center “FIT-ACER checklist applied? (Y/N)”. But even more surprising to me was I heard it coming out of all my teammates mouths on everything we did.
And it works! By taking a few seconds to mentally follow these steps, I’ve found the quality of my work improving dramatically, without hampering my ability to deliver a timely product. I’ve even found myself incorporating the FIT-ACER concepts into my every day life, from following a recipe while cooking dinner to bidding on used video games on E-bay (especially the Identify Authority part – need to get the wife’s approval before buying!).
Ha that’s great Scott! :) So true about identifying the authority lol. Love it. Thanks for the feedback it fuels me.
It seems one of the goals of ITIL framework strictly tailored on dba activities :) … one that allows you to improve the quality of your job and at the same time to meet the strategic goals of your client’s organization.
R for “Review and document results” is one to give the right attention and time: it should be always encouraged to records all the changes made on a system and keep the documentation up-to-date, just to
don’t have to rely on memory, to be more transparent with your client (“this is what I’ve done and this is not”) or to improve efficiency .