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

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People: Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products: These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group . As a service provider, we can’t stop there! We must know what the contracts of our service offering are and be able to put them into context as required by the customer. Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include: Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods. Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you. You the consumer own these and they are yours to take with you. Note: Goods may not always be provided for every Service Offe

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

Search