Skip to main content

The Wisdom Journal

Over my years of teaching and training I have found that some of what I once knew and learned has slipped away due to age (as it does to most of us!) and due to learning new pieces of data, information, knowledge and especially wisdom (D-I-K-W). So many years ago I began to put together a collection of D-I-K-W that I thought was excellent to keep but just could no longer store in my brain. I bought a sturdy, blank, lined journal to begin putting together what has become my “Wisdom Journal”.

I began to collect techniques, approaches, bulleted lists, terminology, tables, tools, methods and anything else that I thought might be useful at some point in the future. I did not really seek out particular information I simply “collected” it as I came along it in my research, class preparation or reading.
Examples of the D-I-K-W I collected included information on paradigms, requirements gathering, RACI, organizational change methods, business process re-engineering, reasoning (induction vs deduction), Six Sigma, causal feedback loops, Deming/Juran/Crosby, meeting improvements, leadership, and a whole host of other topics.
So how did I go about creating my “Wisdom Journal?” After I bought my journal, I split each page into two halves (top and bottom) by drawing a line across each page of the entire journal. As I came across an interesting piece of D-I-K-W, I created a journal entry by putting a simple label at the top of the section and then writing, copying or literally pasting information into that section. Some pieces of information (tables, lists, bullet points, etc.) that were formatted well I simply printed from the web, then cut away the unnecessary pieces of the page and taped the information into the journal entry.
I then took sticky flags (available at any office store) and put one on each page of the journal. I then wrote a general label to the page on the flag. You could also color code the pages using different colored sticky flags. This gave me a quick way to access D-I-K-W quickly and effectively. Over the years my “Wisdom Journal” has proved highly useful. When I need information or knowledge on Strategy, I simply turn to that flag or page and have the information at my fingertips.
Some of you might say that software and applications are available that can accomplish the same thing. This is completely true. But I have found the act of creating the actual journal to be just as satisfying as the collecting of the information. The key is not the particular mechanism (hand-made journal or software application is according to your preference) rather the fact that everyone should create such a collection of readily available and usable D-I-K-W.

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…