I’ve written fairly frequently about death and dying. The concept of non-existence for eternity fascinates me. I suppose that might be a taste weird, but I have a feeling I’m not alone in my wondering. One of my first posts on the subject is about my attitude toward my own death. You can read it here, if you’re so inclined.
I’ve also written about one of my closest friends who was killed in Vietnam, long ago. That post is located here. Another came much later, and is about another friend I had known since before I can remember. I hadn’t spoken with him in a long time and heard about his death from one of his brothers. It can be found here.
I also touched on the subject of grief, somewhat generally, in a post where I ended by lamenting the loss of people I never knew but somehow felt I should have upon hearing from those who were close to them. That post is located here.
All this is merely an intro to a thought I encountered recently on Facebook, and I wanted to share. I think it more than adequately expresses what grief truly is, and how it affects us. What follows is that sentiment. I want to remember it well.
Grief, I’ve learned, is really just love. It’s all the love you want to give, but cannot. All of that unspent love gathers in the corners of your eyes, the lump in your throat, and in the hollow part of your chest. Grief is just love with no place to go.
A lot of airtime has been spent over whether or not Donald Trump offered a quid pro quo to the President of Ukraine, Volodymyr Zelensky. Many astute commentators, however, have pointed out that a quid pro quo is not necessary in this case and, in any event, the real criminal activity here is either bribery or extortion. I would argue that it’s actually both. Let’s look at the elements of bribery.
The individual being bribed is a “public official,” which includes rank-and-file federal employees on up to elected officials; [President Zelensky is most definitely a public official, as is Donald Trump.]
A “thing of value” has been offered, whether it’s tangible (such as cash) or intangible (such as the promise of influence or official support); [Lots of cash was offered to Zelinsky. This is the “Quid.”]
There’s an “official act” that may be influenced by a bribe (such as pending legislation that may have a direct impact on the party offering the bribe); [The Ukrainian government was to make an official announcement it was conducting a corruption investigation into the Bidens and the DNC server. This is the “Quo.”]
The public official has the authority or power to commit the official act (for instance, the official is a senator who is voting on a particular piece of legislation); [Two Presidents . . . duh!]
There must be the establishment of intent on the part of the bribing party to get a desired result (the intent to sway the vote by handing over an envelope full of cash); [The “transcript” of Trump’s call and plenty of testimony], and
The prosecution must establish a causal connection between the payment and the act meaning there must be more than just a suspicious coincidence. [Again . . . lots of testimony from highly credible witnesses to the ongoing attempt at extortion].
It’s become quite clear the American public is a bit uncomfortable with the Latin phrase, quid pro quo and, in fact, as previously stated a definitive “this for that” offer isn’t necessary. Given the totality of the evidence so far, it’s quite clear to anyone who is really paying attention—and understands how the law works—Trump was using the threat of Russian violence to extort an announcement of (at the minimum; actual investigation as they real object) an investigation into Burisma and Hunter Biden.
It can also be argued, at the very least, that Trump was also soliciting a bribe from Zelensky before he would release the money Congress had already authorized for military aid to the Ukrainians. Also offered, in exchange for such a bribe, was a meeting at the White House for President Zelensky.
What’s important to realize is there is no reason to dwell on whether or not there was a specific quid from quo (an offer of something in exchange for something else) to find Trump was engaging in extortion and (as previously noted) at the very least solicitation of a bribe.
That Trump is a common criminal and con man, who has managed to grift his way into the highest office in the land, should be quite obvious to all but those who are now deeply enmeshed in his cult of personality. What this says about that swath of the populace supporting him is quite uncomfortable to fathom. Regardless, I’m looking forward to his impeachment and, if we’re fortunate, removal from office of this deeply deranged and hateful man masquerading as an actual President of the United States of America.
This is another paper I found on my computer. Truth to tell, I have no idea who wrote it. It could have been me, but I don’t remember. I searched the phrase from the title in Google, but could not find anything. Inasmuch as I retired from Rocketdyne (and the pursuit of enterprise-wide KM) nearly 10 years ago, it could be from something I encountered more than a decade ago. Nevertheless, I’m sharing it with the caveat that I’m not claiming to have written it; I’m only asserting it’s an important document for anyone who’s struggling with getting their organization’s people to share their knowledge for the benefit of their company. My experience, as well as my discussion with those who are still involved in the corporate world, is that knowledge sharing is still nowhere near as widespread as I think it should be. So, without further ado, here’s that Baker’s dozen of reasons people aren’t sharing:
don’t know why they should do it. Leadership has not made a strong case for
knowledge sharing. Solution: Have the leader of the organization communicate
regularly on knowledge sharing expectations, goals, and rewards.
don’t know how to do it. They have not received training and communications on
how to share knowledge. Solution: Regularly communicate and conduct training,
webinars, and knowledge fairs. Web-based training and webinar recordings should
be available for all tools.
don’t know what they are supposed to do. Leadership has not established and
communicated clear goals for knowledge sharing. Solution: Establish and
communicate clear knowledge-sharing goals.
think the recommended way will not work. They have received training and
communications but don’t believe what they are being asked to do will work.
Solution: The KM leaders, knowledge brokers, and other members of the KM team
have to convince people in small groups or one-on-one by showing them that it
think their way is better. They are used to working on their own or
collaborating only with a small group of trusted comrades and believe this is
the best way. Solution: Regularly share stories of how others are benefiting
from sharing knowledge using the recommended ways. This should help sway those
stuck in their current ways to consider using better ways.
think something else is more important. They believe that there are higher-priority
tasks than knowledge sharing. Solution: Get all first-level managers to model
knowledge-sharing behavior for their employees, and to inspect compliance to
knowledge-sharing goals with the same fervor as they inspect other goals.
is no positive consequence to them for doing it. They receive no rewards,
recognition, promotions, or other benefits for sharing knowledge. Solution:
Implement rewards and recognition programs for those who share their knowledge.
For example, award points to those who share knowledge, and then give desirable
rewards to those with the top point totals.
think they are doing it. They are sharing knowledge differently than the
recommended ways (e.g., sending email to trusted colleagues or distribution
lists). Solution: Assign people to work with each community and organization to
show them how to use the recommended ways and how they work better than other
ways. Providing a new tool or process which is viewed as a “killer app” – it
quickly and widely catches on – is the best way for the old ways to be replaced
with new ways.
are rewarded for not doing it. They hoard their knowledge and thus get people
to beg for their help, or they receive rewards, recognition, or promotions
based on doing other tasks. Solution: Work with all managers in the
organization to encourage them to reinforce the desired behaviors and stop
rewarding the wrong behaviors.
punished for doing it. As a result of spending time on knowledge sharing, they
don’t achieve other goals which are more important to the organization.
Solution: Align knowledge-sharing processes and goals with other critical
processes and performance goals.
anticipate a negative consequence for doing it. They are afraid that if they
share knowledge, they will lose their status as a guru (no one will have to
come begging to them at the time of need), that people they don’t trust will
misuse it or use it without attribution, or that they will not achieve other
more important goals. They are afraid of asking a question in public because it
may expose their ignorance or make them appear incompetent. Solution: Position
knowledge sharing as being a critical success factor for the organization.
Facilitate ways for people to establish trusting relationships through enterprise
social networks and face-to-face meetings. Recognize those who ask in public,
and provide ways to ask questions on behalf of others.
no negative consequence to them for not doing it. Knowledge sharing is not one
of their performance goals, or it is a goal which is not enforced. Solution:
Work with all first-level managers to get them to implement, inspect, and
enforce knowledge-sharing goals. This needs to come from the top – if the
leader of the organization insists on it and checks up on compliance, it will
obstacles beyond their control. They are not allowed to spend time sharing
knowledge, they don’t have access to systems for knowledge sharing, or they
don’t have strong English language skills for sharing with those outside of
their country. Solution: Embed knowledge sharing into normal business
processes. Provide ways to collaborate when not connected (e.g., using email
for discussion forums). Encourage those with weak English skills to share
within their countries in their native languages.
the current move toward gathering, cataloguing, storing, and disseminating
information and data for widespread organizational use is a fairly recent
development, the basic concepts of Knowledge Management have been with us for
as long as humans have gathered in communities. Humans have always struggled
with the need to pass on information gathered through hard experience and
his new book, to be published this fall, Steven Denning sets forth a brief
synopsis of the human activities which have preceded our current drive toward
Knowledge Management. In it he states, “The pursuit of any significant
human activity typically leads to the acquisition by those involved of know-how
and expertise as to how the activity may be successfully conducted. Insofar as
what is learned in the process can be captured, and communicated and shared
with others, it can enable subsequent practitioners – or even generations – to
build on earlier experience and obviate the need of costly rework or of
learning by making the same repetitive mistakes.
“In the village, from time immemorial,
the elder, the traditional healer and the midwife have been the living
repositories of distilled experience in the life of the community.
Interactive knowledge-sharing mechanisms
have always been used – from palavers under the baobab, village square debates,
and town meetings, to conclaves, professional consultations, meetings,
workshops, and conferences – all functioning to enable individuals to share
what they know with others in the relevant area of knowledge. “
(emphasis the author’s)
1988, as the pace of change was accelerating with the rapid development and
deployment of large-scale information systems, Peter F. Drucker observed,
“Information responsibility to others is increasingly understood, especially in
middle-sized companies. But information responsibility to oneself is still
largely neglected. That is, everyone in an organization should constantly be
thinking through what information he or she needs to do the job and to make a
understood then the pivotal dilemma with respect to data and information now
being faced by many organizations, that of understanding its power and devising
the methodologies whereby it can be harnessed and used to the benefit of the
people who need it to perform their jobs properly.
referring to information specialists as toolmakers, Drucker said, “They can
tell us what tool to use to hammer upholstery nails into a chair. We need to
decide whether we should be upholstering a chair at all.
and professional specialists need to think through what information is for
them, what data they need: first, to know what they are doing; then, to be able
to decide what they should be doing; and finally, to appraise how well they are
doing. Until this happens MIS departments are likely to remain cost centers
rather than become the result center they could be.”
MIS departments are still struggling with the notion of becoming “result
centers”. Too frequently, they concern themselves with the infrastructure of
the organization’s data processing capabilities, and completely ignore the role
Knowledge Management (in its broadest sense) can play. Instead of leading the
way through the morass of competing needs, whether perceived or real, they find
themselves being led around by various departments seeking to have their agenda
legitimized, often to the detriment of the MIS department’s ability to serve the
company as a whole.
Rocketdyne, which employs a large percentage of well-educated, highly computer
literate individuals, there exists a great deal of enmity between the users and
the Information Systems (IS) department. There are many who feel the department
should fulfill the role only of providing the infrastructure, i.e. the
telecommunications backbone and the hardware, and maintaining its reliability.
These people believe IS has abdicated its responsibility of providing guidance
for software development and acquisition, through an historic ineptness in
performing this function.
this view is accurate or not, it demonstrates a division which has long been
developing and will not soon go away, especially without visionary leadership
schooled in the concept of Knowledge Management. Many knowledgeable workers at
Rocketdyne believe they must have the freedom to purchase software which will
support their needs, or to develop that software without interference and
second-guessing by the IS department.
question which looms now for most organizations, and certainly for Rocketdyne,
is how can the data which is both created and collected be harnessed for the
purpose of continuing a company’s pursuit of its goals.
we are experiencing, I believe, is a time of challenge and opportunity.
Historically, humans have always valued the hard-earned wisdom of our
forebears. We rightly believe in the inappropriateness of “reinventing the
wheel”, and we have continuously improved on our methodologies for categorizing
and memorializing the lessons we have been taught or have learned through
Management is merely the application of this historical pursuit of know-how and
expertise to the comparatively new tools we have developed. The concept itself
is nothing new, The question then becomes one of how do we go about harnessing
these tools to our advantage; how do we make that quantum leap into an entirely
new way of viewing an old problem.
the next section we will look at a little bit of the background of the present
day approaches to Knowledge Management, and see how companies are beginning to
recognize the necessity of understanding and utilizing this approach to
conducting business and running an organization successfully.
I’ve begun work on something I have wanted to do for a long time but, for numerous reasons (some of which actually make sense in retrospect) have not been able to accomplish. I’m speaking of writing a book. Actually, I’ve had three books in mind for a few years: One sharing my blog posts; one about the years I spent in the Peace & Justice movement, with special emphasis on the movement against the war in Vietnam; and, my memoirs. I can say with reasonable objectivity, I have had a rather unconventional and interesting life.
Since the beginning of March of 2018, I have been working part-time as the business manager for a small AI software development firm. In doing so, I transitioned from my Mac to a PC laptop in order to comply with the company standards. Today I moved my Mac out into a place in our living room where I can sit quietly and write. Since this is the first time I’ve actually spent a while at the Mac, I have been going through my files and am somewhat pleased to discover there are a lot things I’ve written over the years that should prove helpful in writing (at least) my memoirs. Some of the things I’ve written are only a couple of sentences or a paragraph or two, but they convey the essence of a thought I can expand upon. On the other hand, some of them are completely unintelligible.
What I’m going to do here, however, is use this blog to publish a term paper I submitted 19 years ago, when I was attending classes at California Lutheran University, in their Center for Lifelong Learning offering, ADEP (Adult Degree Evening Program.) It’s 22 pages long, so I’m going to post it in sections, as I wrote it. Today I’m sharing the intro. As I’ve re-read parts of it, I’m reasonably certain some will end up in at least my memoirs, as they are part of my unusual education.
this paper is being written as part of the requirements for a grade in
Organizational Management, its impetus and content are driven by a real life
situation at the company I work for, Rocketdyne Propulsion and Power, a
business unit of the Space and Communications Division of the Boeing Company.
As suggested in the course syllabus, I selected a subject which I felt had some
relevance to my company’s activities and my position within it.
with many organizations throughout the world, mine is struggling with
understanding and implementing the concepts of Knowledge Management. These
concepts, and the issues surrounding them, are numerous and complex. As an
example, one question which must be asked is how does an organization determine
the importance of the information it uses and how does it weight that
importance? How does it determine who needs it, who wants it, who might benefit
from knowing of its existence, or whether or not it should be available to
everyone who might wish to make those determinations for themselves?
there are numerous software developers who are touting their particular method
of capturing data and making it available to a company’s workforce. Each of
these developers will attempt to convince you their method is best for your
application. Of course, this situation is hardly different from that faced by
anyone who has to determine what method they will use, or what software they
will purchase, for any task. Nevertheless, at this early stage of the game it
doesn’t make the task any easier.
propose, in the following pages, to set forth some of the history of Knowledge
Management, from tribal times to today, and the perceived need for Knowledge
Management, both in general, and with particular emphasis for my company,
Rocketdyne. I will look at what knowledge management means, and briefly mention
some of the tools which are being used to develop its use. The definition of
tacit knowledge, and the importance of understanding it when implementing
Knowledge Management will be discussed, along with a brief look at how we
acquire and share knowledge. I will close with a glance at what is probably the
most daunting task facing a company which desires to utilize Knowledge
Management to its advantage, the need for dramatic cultural change.
beginning, however, I would like to quickly explain the nature of this paper’s
subtitle, “Breaking the Information Bottleneck”. Here, the word
bottleneck has the same meaning we use when speaking of a traffic jam. Most of
us have experienced being caught on the freeway when suddenly we come to a
crawl or dead stop. Usually there is an explanation for the delay. Sometimes,
however, there is no apparent reason.
the same way that freeways experience bottlenecks, so too does any system which
requires the smooth flow of some activity or commodity. On the shop floor, it
is generally components, though it can also be tooling, raw material, or usage
hardware. In the office it is generally data or information, and when its flow
is restricted the organization suffers.
believe, with the advent of computers, and their widespread use through Local
Area Networks and intranets, and with our increasing dependence on technology
to solve our problems, we have forgotten how sharing knowledge actually works
and, in the process, created huge information bottlenecks which will not go
away until we learn once again how to manage knowledge.
the scope of this paper is woefully inadequate to fully treat all the issues
involved in this major change now occurring. It is my hope that I will be able
to expand upon and use it to help melt the glacier of resistance which
surrounds my organization at present and makes change painful and tedious.
no mistake. Trump, Barr, Pompeo, Graham, and numerous others are not
merely corrupt. They are enemies of the United States of America.
Despite cries of “America First” and assertions they are working for us,
they are financial internationalists. They don’t give a rip about
anything other than their next grift and they will sell us down the
river if there’s anything to be gained for them. We will continue to
decline as long as they hold the reins of our—repeat, our—government.
I’m happy impeachment hearings are finally under way, but we need to
pay close attention to everything that’s going on, and we need to be
ready to take matters into our own hands. I’m taking about organizing,
demonstrating, marching, striking, boycotting, and whatever it takes to
fight back. Our health, our wealth, our freedoms, and everything we hold
dear are being slowly eroded by people who have neither the right, nor
the desire, to be public servants.
Eyes on the prize, my friends.
And make sure you elect progressives to every local office you can:
Park Board; Board of Education; City Council; Mayors, etc.
In addition to the newsletters I’ve published over the years, I’ve also done some promotional work for various businesses and reasons. This was a flyer I put together for a fundraiser at Simi Hills Golf Course, where I learned to play at 46-years-old. This means I’ve been playing golf for 26 years, which I have a hard time believing. Of course, when I became a first-time, adoptive father at 55, it definitely put a cramp in my style and I’m only now reaching a point where I think I might have time to play and practice a bit more frequently. Not sure I’ll be able to afford it, though.
Here’s the second issue of the KM newsletter I wrote and published for the SSME KM team. This one was for January of 2006. The middle column has a couple of decent descriptions of “Lessons Learned” and “Best Practices.” What it doesn’t address, which is something many of us came to understand later, is that we don’t actually want “Best” Practices; which implies there won’t be any room for improvement, as “best” is a superlative adjective, which means it just doesn’t get any better than best. We, therefore, preferred to talk about “Better” Practices, which also fits rather nicely into the philosophy of continuous improvement. My apologies if this is boring.
At the end of 2005, I was still five years away from accepting an early severance package from Pratt & Whitney Rocketdyne and then retiring a couple years early. I don’t think the Shuttle program had yet been cancelled, so everything appeared to be full steam ahead. I had been deeply involved in developing the concept of Knowledge Management (KM), primarily to the Space Shuttle Main Engine (SSME) team—for which I was the lead—as well as for the entire organization, from its ownership by Boeing to a subsequent purchase and merger with United Technologies’ Pratt & Whitney Division.
So, there were two teams I was involved with: the corporate, enterprise-wide team, and the SSME team. I had convinced my management to start the SSME team before I knew there was a corporate team, and it was my primary focus of attention at the time. Starting in December of 2005, I published a newsletter for the team; a KM newsletter, ostensibly by the SSME KM team for the entire SSME program team.
When I returned to work for a couple of years at Rocketdyne in 2015, I was able to find pdf files of every issue of that newsletter, which we called “quicKMemos.” I’m am converting these pdf files into png files so I can upload them here. I’ll post them somewhat sporadically, no doubt, as I have several duties and obligations that are always tugging at my sleeve and demanding my attention. So . . . here’s the first one; Vol. 1 No. 1, December 2005.
NB – Check out the Eleven Deadly Sins of KM. They still seem relevant to me, though it’s hard for me to tell as it’s been nearly 10 years since I’ve been in a large enterprise environment.
Born in 1947, I am an officially retired pensioner who still has two teenage daughters and a desire to contribute. I remain intensely interested in, and fascinated by, Systems Thinking, Machine Learning, Knowledge Management, Decision Intelligence, and Business in general. I am also conversant in such concepts as innovation and ideation, collaborative tools and strategies, crowdsourcing, and the use of social media to accomplish goals ranging from improving business processes to promoting small retail businesses. Since my "retirement" I have done a little bit of freelancing as an editor/proofreader, as well as some technical writing. I've also done a fair amount of Facebook marketing as well.
There's lots more where that came from. Need some help? Perhaps another set of eyes? Contact me. The first one's free! ;0)
The views expressed herein are those of the author. Any opinions regarding the value or worth of particular business processes, tools, or procedures, whether at his former place of employment, at a current client's enterprise, or in general, are his responsibility alone.