Learning To Solve For Pattern

Isaac Newton is credited with the observation that “If I have seen further it is by standing on the shoulders of giants” (which he actually appears to have borrowed from 12th Century philosopher Bernard of Chartres. see (Standing on the Shoulders of Giants). Computer scientist Richard Hamming was a bit less gracious, and perhaps more relevant, when he pointed out that “In computing, we mostly stand on each other’s feet.”

Both men were clear, however, that progress builds on the work that came before. This is an axiom in academic disciplines. Becoming an effective academic starts with long apprenticeships centered on immersion in the context of a field. You don’t get to play until you can demonstrate that you are familiar not just with the forms but the substance of what has come before.

Familiarity with context and history has not been so axiomatic outside of ivy-covered halls. For much the industrial revolution, the story has been about what is new, different, and innovative. Men of action were rooted in the now and facing tomorrow.

As more economic activity depends on those who think for a living, that equation has been changing. The old canard “those who can, do; those who can’t, teach” has lost much of its currency. At the very least, we need to stop standing on one another’s feet.

Claiming that your new product or service is new and different is easy to do if you don’t bother to look around you. Too many careers have been built on confident assertions without evidence. I suspect that the continuing popularity of connecting the dots arguments is partly anchored in the hope that confidence will out.

Solving for pattern, on the other hand, starts with accepting that you don’t, and can’t, know everything. While there won’t be a specific picture hiding in the data, there will be fragments and familiar elements that can be discerned, however incompletely. Your job is not to match what you see against a standard, it is to construct a plausible story and make sense out of what you think you are seeing. There is no passive role to adopt.

Stop Trying to Connect the Dots

Connecting the dots is a fun children’s game. It’s a lousy strategy for making sense of complex phenomena.

As a game, it’s fun to see a picture emerge as you drag your pencil from dot to dot. When it’s used as a metaphor for sensemaking in the real world, there are a set of hidden assumptions that are particularly pernicious because they are hidden. In the game, you start from a picture, select and number a collection of dots, and then erase the rest. You simplify a complex image into a subset of data points and a prescribed sequence for connecting the dots.

This is not a reversible process. You cannot collect a set of dots, connect them as you choose, and then claim that the image was sitting there all along. Nor can you criticize an analyst for failing to collect or connect the necessary dots in advance. It’s lazy language and lazy thinking.

While lazy thinking, it’s also rampant. Cast your mind back to your university days. It’s a safe bet that you had a course syllabus with extensive verbiage about academic integrity and the perils of plagiarism. And expectations for preparing terms papers laden with correctly formatted references to the literature you consulted as you did your research. Fail to include the proper incantations in your submitted work and you were at risk of dire punishment.

All of which encourages connecting the dots thinking and discourages developing the more robust skills of solving for pattern that you are going to need to tackle the open-ended and complex problems you will encounter.

 

 

Forcing Functions To Understand Complex Work

From time to time, I get invited to speak to groups of executives. I’ve even gotten paid to do so and been invited back for repeat performances. What I haven’t done is develop an inventory of stock speeches. That can be an effective and lucrative path for those who opt for it. But, that path is premised on having a message you want to share widely. It’s more about preaching and I am more interested in teaching.

Here’s an example from about a dozen years ago that might tease out the distinction. A software vendor I’d worked with asked if I would keynote their annual users group meeting. They were (and are) a player in the corporate knowledge management space. As a former Chief Knowledge Officer for a growing management consulting firm, I was trying to work out why certain efforts had failed and others succeeded only modestly.

I treated the invitation as a forcing function; an opportunity to work out some thinking with an audience who might have insights to share. Consider it a segment in the longer process of solving for pattern.

A persistent problem in corporate knowledge management efforts was getting knowledge workers to share their work more broadly. Various incentive and control systems didn’t appear to have much effect. The premise behind these solutions was that people were reluctant to share their work for reasons unknown.

I used this event to explore an alternate hypothesis; sharing knowledge work was hard to do because technology made the doing of knowledge work invisible. Work that had been visible in the movement and flow of paper or the flipcharts and whiteboards in conference rooms had disappeared behind the keyboards and screens of workstations, personal computers, and laptops. Solving the sharing problem was not about incentives, it was about visibility. Make knowledge work observable and sharing becomes more natural.

 

Honor the Work

John Cusack’s first movie The Sure Thing is one of my favorites. In one scene, Cusack’s college roommate is explaining his success bedding a string of random coeds; “It’s all about sincerity; once you can fake that the rest is easy.” Cusack’s character arc is all about his inherent sincerity and learning to let it through in place of the games he thinks he should play.

It’s a constant challenge to stop looking for shortcuts and do the work. This is my fundamental objection to the language of “connecting the dots” It perpetuates the mythology of shortcuts. It puts the focus on the final step, the reveal.

“Solving for pattern” shifts the emphasis productively. Wallowing in the phenomena to identify things that may or may not turn into a dot. Trying out different combinations, connections, and clusters to see whether they point to something interesting. Formulating and testing hypotheses that might explain what you are observing.

I grew up wanting to be a scientist; preferably a rocket scientist based on the dominance of science fiction in my reading habits. As I found myself drawn more and more to the human side of the equation, I questioned that dream. Things were too messy to fit into the narrow conception of science I had started with. I was confusing the pretty pictures with the underlying discipline of the process.

Solving for pattern starts from designing with heart

One task for this weekend is to complete a letter of recommendation for one of my recent students. You get these if you are reasonably approachable and care. It’s a moment of vulnerability that you want to be careful of.

It’s set me to remembering similar processes I’ve been part of. For many years, I interviewed high school students applying to the university I attended. You were expected to forward your thoughts and recommendations to the admissions committee. I don’t know that those insights had the slightest impact on the admissions process from the school’s perspective. But that wasn’t why I chose to participate.

Instead, I thought back to that time when I was on the other side of the process as a nervous high school student. This was long before students routinely visited multiple college campuses in their quest for the perfect undergraduate experience.

My father had gone to college on the GI Bill after serving in the Navy during WWII. My mother did a year or two of college before going to work and then starting a family. No one else in our extended family had done even that much.

I was attending a pretty exclusive private high school and being pushed toward even more exclusive universities with no basis for making any sense out of the process I was flowing through. Graced with acceptances to two of those universities, how was I to make an informed decision? It came down to my experience sitting across from an alumnus from each of the schools in one of those ritual interviews.

One conversation focused on how the school would serve as a stepping stone to a great future and the tradeoffs and challenges I might have to navigate. The other was a mix of nostalgia for their experience and envy that I was about to embark on a journey they would happily take again if they could walk in my shoes. It shouldn’t be hard to guess which path I chose to walk.

In one case, the process devolved into a connecting the dots experience. The surface elements were there, but there was no heart. In the second, the surface elements tied into deeper patterns and that produced the necessary heart.

Effective Knowledge Work Environments Start From Design

Like yours, I suspect, my inbox is littered with a steady stream of pitches. A few are even from sources I’ve given permission to contact me. Nearly all follow a standard formula (except for the ones promising to teach me that formula); they describe some imagined pain I am experiencing and promise that their product/service/”proven system” will eliminate my pain and bring me joy/riches/satisfaction/relief. All for the low, low, price of “click here” to dive deeper into their sales funnel.

Makes buying a used car a veritable day at the beach.

If you’re in the market for diapers, a new pair of shoes, or that used car, this strategy is annoying but it does work. It’s also rooted in a set of assumptions that conflict with the assumptions necessary to carry out competent and effective knowledge work.

These pitches are “connecting the dots” thinking applied to “solving for pattern” problems. Ignoring that distinction may tempt you into parting with your money in exchange for things that address your problems only by accident. In a connecting the dots world, problem solving is a selection process. In a solving for pattern world, it’s a design process.

For knowledge problems there are no off-the-shelf solutions that you can simply buy. There are no proven systems to adopt and roll out. The best you can hope for is good guidance on how to tailor available tools and practices to your unique circumstances.

Step 0 is recognizing that you have to start with design. Hard to evaluate prospective solutions until you’ve developed a deep understanding and appreciation of the problem at your hand. We are so accustomed to being offered answers that it is too easy, and tempting, to forget that you need to start from a well-articulated question.

Follow the Markers to the Patterns

Many years ago I inherited the Christmas Pageant at our church. Each Fall, Melissa, our Director of Children’s Ministries, reaches out and asks whether I am willing to do it again, I allow as how I had little choice and say yes, another Pageant unfolds, and I can count on a lovely little thank you note from Melissa.

Come next year, I will be several thousand miles away when Christmas rolls around. We began the process of turning over the Pageant to new leadership. Amanda shadowed me this year to discover how much of the work and leadership I had turned over to our high school parishioners. They have all been through the process multiple times, first as angels and sheep, then as shepherds and readers, and finally as directors. My “leadership” consists of giving the older kids space and permission to take ownership of the effort.

The names and faces evolve but the pattern holds. It’s the pattern that I look for and try to understand. Things like the emails and thank you notes are the markers. If the markers lead you to the patterns, that’s good. Markers by themselves are troubling.

Learning to Make Your Own Sausage

I’ve long been an advocate of case method teaching and learning. Jump into the deep end of the pool and hope there are some lifeguards around when you get into trouble. Good cases are a way to mimic the messiness of the real world in a safe and controlled way.

Learning to write those cases was yet another level of learning by doing. There is craft in taking real messiness and packaging it so that the feeling is real but the risks of drowning are contained. Teaching cases typically have a layer of supporting notes for instructors to help them manage the experience.

When you are in case and course design mode, you are often on the lookout for situations that will help you set up and drive home the learning points you are trying to make.

What happens as you get to the edges of what is known? You don’t know enough yet to separate the signal from the noise. You’ve left the safe confines of the pool, you’re in open water, and the lifeguard might also be thrashing next to you.

I had one particular professor who supervised the cadre of doctoral students. Classes with him were not a carefully orchestrated simulation of a case. They were much more like an improv class, although I didn’t have that reference point at the time. He opened up his own thinking process in real time. We watched and followed along as he dove into the mess at hand. As he talked through a line of thought, keywords got jotted down at seemingly random spots on the whiteboard, arrows were drawn between words, other phrases were circled for emphasis (sometimes multiple times over the course of the session), names and references were tossed out in a rush. I typically left that class in a daze with a pile of incomprehensible notes.

The curious thing was that I also typically woke up around 2am the following morning with some flash of insight. At first, I simply thought he was simply a bad teacher. Surely, he could have laid things out crisply and neatly. It took a much longer time for me to understand what was going on. He was teaching us how to swim and survive in open waters. Not something you can do from the shore or inside the lanes of a pool.

The professor’s goal here was to increase our skill at making sense out of complex situations. And that sense was a synthesis of the facts at hand and the perspective we each brought to the situation. It wasn’t about trotting out a textbook answer. It was learning how to invent a better answer than anyone else had come up with yet. They say that no one wants to see how the sausage gets made. Unless you want to learn how to make sausage for yourself.

Deciding where you want to play

My Mom passed away almost twenty years ago.┬áMom was an anarchist at heart. She tolerated authority when it suited her; ignored it when it didn’t. As her first born and brighter than average she was inclined to trust my reports about school over those of my teachers. One practice that grew from that trust was my ability to take a “mental health day” whenever I thought it necessary. No questions asked, Mom provided the necessary support. She trusted my judgment and was willing to subvert the official system accordingly.

I wonder whether this was one of the seeds that grew into my fascination with organizations and systems. They are inventions of human ingenuity and reflect the design assumptions of their inventors. If you choose to participate in a given organization or system, you can do so blindly or mindfully.

Most organizations aren’t very carefully designed. They’re fuzzy copies and collages of other organizations we’ve experienced. And too many of those fuzzy images are rooted in old industrial assumptions about the weaknesses of “other” people. Half the HR policies in many organizations exist to make sure that no one ever does what John or Jane did that one time.

The deeper problem is that you provoke the behavior you expect. If your designs assume that people can’t be trusted that is the behavior you are more likely to see. It works the other way as well. Something to always keep in mind when you decide which organizations and system you want to play in.

Making expert sense of the facts at hand

It was a stupid little accident on a Saturday afternoon. I fell over on a bike traveling about two miles an hour. But I landed oddly on my shoulder and knew something wasn’t right. My wife drove me to the ER and the verdict was a broken humerus. I was given a sling for my arm, pain meds, and instructions to see my primary care doc on Monday. On Monday, my regular doctor thought there might be more going on based on his reading of the X-ray and sent me off to an orthopedic surgeon. After more X-rays and an MRI the diagnosis grew more ominous. What I actually had was a “comminuted fracture of the right proximal humerus.” What I had done was to crack the top of my humerus like an egg. After several hours of surgery I ended up with multiple screws and a steel plate putting everything back where it belonged. A year’s worth of physical therapy got me back to about 90% of normal.

One of the things that struck me during this process was the interplay between information and expertise. Pain and the inability to move my arm more than a few inches told me pretty clearly that something was wrong. The initial X-ray provided a bit more information but the expertise in the ER was only enough to pass me along to the next experts. More imaging technology combined with more specialized expertise brought me into the operating room. Even then, I had to authorize several options before my orthopedic surgeon could start the surgery. He wouldn’t know until he opened me up whether he could repair the shoulder or would need to replace it. I was lucky, he was good, and a repair was sufficient.

Facts don’t speak for themselves. There’s always a storyteller picking, choosing, and interpreting the facts. Technology can often reveal new details and new facts. But they all depend on a storyteller to make sense of the facts at hand. And sometimes, the right expert has to go and observe directly.