We use necessary cookies for the functionality of our website, as well as optional cookies for analytic, performance and/or marketing purposes. Collecting and reporting information via optional cookies helps us improve our website and reach out to you with information regarding our organisaton or offer. To read more or decline the use of some cookies please see our Cookie Settings.

Skip to content

Do not breach an open door

Mar 3, 2016 - 1 minute read

Objectivity Blog 416 306
Piotr Torończak
Recently a Software Engineer in Support. SQL Server practitioner and former DBA. In Objectivity Blog I write about a Support life and problem solving techniques. Privately a guy with no passion, but many interests. A hiker, an MTB rider, a reader and jazz music aficionado.
See all Piotr's posts
Healthcare Ebook News Insights

Share

Take a close look at a set of certain practices at one of the world's top strategic consulting companies (they've advised most companies from Fortune 50, 100, 500, 1000, and they don't advertise - they don't have to). First of all, they keep a browsable database of "clean" reports from past projects (clean means no company names or sensitive data are enclosed). Second, their consultants can contact any of the other consultants around the world for advise/tip/hint, and those are obliged to respond within 24 hours (if possible).

Keeping an internal knowledge base around is so underrated. Solving an overnight crash (either at 2AM or on a misty day, your thinking performance is not state-of-the-art) gets so much easier when you have some notes with previous solutions saved. Your colleagues might also "have been there and done that."

You may want to argue that do-it-on-your-own attitude is better (for the sake of learning). There are three proven ways of learning: by studying, by doing and by examining how others made it before. So if you really insist, keep that option around when you have some spare time.

Hide your pride. Keeping a strong culture of knowledge exchange goes along with superior quality and performance, bolsters creativity and teamwork. Coming across a tough problem doesn't indicate a hard mining for solution. Go through your team's shared notes/documents, ask around. A key to that closed door may lay around, don't waste your time breaching it.

PT

Healthcare Ebook News Insights
Piotr Torończak
Recently a Software Engineer in Support. SQL Server practitioner and former DBA. In Objectivity Blog I write about a Support life and problem solving techniques. Privately a guy with no passion, but many interests. A hiker, an MTB rider, a reader and jazz music aficionado.
See all Piotr's posts

Contact

Start your project with Objectivity

CTA Pattern - Contact - Middle