Tim’s Takeaways: Tribal Knowledge—Not the Villain You Thought

There’s a lot to be said about the pros and cons of tribal knowledge in the workplace and there really is more than one definition. To put it simply, tribal knowledge is information or skills known by an individual or group that is not known outside that group. One of the trademarks of this definition is that it’s commonly used to describe functional—but undocumented—knowledge essential to the operation of an organization. Of course, this is a broad generalization and just one definition of tribal knowledge, but it will do for our purposes.

There are good reasons these undocumented processes are usually looked on as a liability. For example, the smooth operation of a PCB design group requires specific functional skills and knowledge. If this information isn’t accessible through clear and concise documentation, it can only be passed from one employee to another through mentoring or by example. Without proper documentation, critical operational knowledge and procedures can be lost. This can be due to employee turnover, or like the children’s game Telephone, it can become confused and misapplied. After passing from person to person, the final state of a secret message in the game is often hilariously altered from how it originated. In the workplace, however, wasted time and effort aren’t nearly as amusing, especially when it results in lost revenue because those processes and procedures were misunderstood.

It can reasonably be expected that an experienced PCB designer will understand how to lay out different technologies of circuit boards: digital, analog, power, RF, etc. However, a designer won’t necessarily understand the design flow, critical layout techniques, and manufacturing data requirements of a specific company, especially if they are new to the organization. Even something as simple as, “Our standard trace width in this application is X,” can end up as an error if it isn’t properly documented. Although it is true that the newer output file formats, such as IPC-2581, can help mitigate complex procedural problems, such as learning file generation processes, there are still many hurdles caused by tribal knowledge that must be overcome. These include understanding specific manufacturing processes, design documentation details, and specific legal or certification requirements, to name a few.

Another problem with tribal knowledge is how those processes can become stale with time due to the inability to review, refresh, and update undocumented procedures. It makes you wonder just how many errors have been introduced into designs because the “tried and true” methods embedded in tribal knowledge are hopelessly antiquated, which allows mistakes to happen. Along those same lines, how much unnecessary effort has been expended and time lost due to outdated processes still in place? For instance, many newer design systems will automatically track and propagate part numbers and descriptions. Yet some people will still manually record this information because “that’s the way we’ve always done it.”

So, tribal knowledge is bad, right? Well, maybe not in all circumstances. I would agree that relying on undocumented processes to convey critical procedural information can, in some circumstances, lead to negative or even catastrophic results. But there are some positive outcomes when relying on tribal knowledge as well. Consider the following story of how I once benefited from someone’s tribal knowledge in a completely unexpected way.

Years ago, we moved across town from one house to another. I hired a moving company to do the heavy lifting for us and went with them to supervise the first delivery. However, I witnessed a terrible sight when we returned for the next load. A landscaper hired by the new owner already had ripped out all the existing plants and bushes, as well as unloaded all the new shrubbery on the driveway. Since this is Oregon, it was raining cats and dogs, and the dirt from the new shrubs was creating a sea of mud over the entire driveway. I was in total shock and had no idea how to resolve this situation. We still had a large amount of furniture and possessions to move, and my driveway was completely inaccessible.

At this point, the moving crew supervisor noticed my “deer-in-the-headlights” expression and realized that I was completely incapacitated. Springing into action, he said quite firmly, “Tim, you stay here, and I will take care of this problem.” Hopping out of the truck, he demanded to know who was in charge of the landscape team and then laid down the law very succinctly to their supervisor: “We are moving the previous homeowners out of this house today and will be using this driveway. If the new homeowners don’t want us to drag mud through their brand-new house, you will have this driveway cleaned off in five minutes so that we can proceed.” With the landscapers properly chastised, in very short order we had a clean driveway and proceeded with the move.

I hope the new owner loved our former house as much as we did and ended up with a beautiful yard of new plants and bushes. My point in relating this story, however, is in how the moving crew supervisor used his experience to save the day. I was having a crisis moment, and needed someone who knew what to do and wasn’t afraid to use their knowledge to get the job done. Yet, if you were to look up the processes and procedures for this moving company, I will bet that there wasn’t a single piece of documentation that detailed how to handle a mud-caked driveway filled with shrubbery. Instead, to successfully solve the problem, this supervisor relied on his past experiences in dealing with various scenarios and his gut instincts.

Obviously, documented procedures are essential. But it’s important to react to unique situations with only our experiences and knowledge to guide us; this is what some would label as reliance on tribal knowledge. There is a fine line here, and, realistically, the need for both is important. Considering this, how can we manage tribal knowledge within our organizations to ensure that we get the best results no matter which course of action is required? Here are some ideas.

Facilitate Open Communication
Isolation is a negative aspect of tribal knowledge that should be avoided. Without the ability to freely share information between co-workers, critical procedures will inevitably get siloed by groups or individuals, bringing about the bad results we’ve discussed. Instead, ensure that communication with your co-workers is unencumbered by either technology or company culture. Open communication gives everyone a stake in the game and helps bring to light important process steps that are all too often known only to a few.

Keep Documentation Up to Date
If you don’t want the critical processes in your workflow relegated to tribal knowledge, it’s essential that you keep your documentation fresh. This requires regularly scheduled reviews of your procedures and putting a system in place for workers to report outdated or incorrect processes.

Make Documentation Easily Accessible
Another important but often overlooked element of good documentation is its accessibility. How many times have you needed a procedure, and yet you couldn’t quickly find what you were looking for? As corporations grow, so do their file systems and documentation processes. Workers may not know where to look for their procedures or that they even exist in the first place. One of the quickest ways to foster the creation of unwanted tribal knowledge is to bury important process documentation so deep that no one can find it.

Encourage Initiative
Even with all the best documentation in the world, there will be those times when someone must deal with a muddy driveway. To ensure that your corporation doesn’t stall out when critical non-standard decisions have to be made, encourage your team to feel they have the initiative and freedom to do so. You may lose control in some circumstances, and there may even be a few errors, but if you want to be ready to handle the unexpected, it requires some risk. You will develop greater operational flexibility in your company, foster a new sense of ownership, and encourage a desire to excel.

In my company, we have reorganized our department into smaller vertical teams that focus on different areas of the business. Not only has this helped our overall department efficiency, but the smaller team structures have opened communication between co-workers, which fosters the development of new processes and procedures. One example is how the teams have initiated cross-functional training to better support each other in overload situations. Instead of allowing work to pile up when the one person trained to do that job is unavailable, the work can now be spread around; this prevents a bottleneck. By freeing up our teams to take the initiative, they identified areas that have improved the workflow and increased our productivity.

So, is tribal knowledge good or bad? I would say it’s a little of both. The best approach is to find the parts of tribal knowledge that are most useful, then harvest and manage them for the benefit of the entire corporation. What do you think?

Until next time, everyone, keep on designing.

This column originally appeared in the March 2023 issue of Design007 Magazine.



Tim’s Takeaways: Tribal Knowledge—Not the Villain You Thought


There’s a lot that can be said about the pros and cons of tribal knowledge in the workplace and there really is more than one definition. To put it simply, tribal knowledge is information or skills known by an individual or group that is not known outside of that group. One of the trademarks of this definition is that it’s commonly used to describe functional—but undocumented—knowledge essential to the operation of an organization. Of course, this is a broad generalization and just one definition of tribal knowledge, but it will do for our purposes.

View Story

Tim’s Takeaways: Threading the Needle Through Advanced Packaging


Last week my wife started a new project that required a trip to the craft store for supplies, and she invited me to join her on this errand. This is not the first time I’ve faced this scenario; do I choose to follow her around the craft store pushing the miniature cart that will, by the time we get to the register, barely contain all her chosen fabrics and materials, or stay at home and watch TV? Thankfully, by this point in my life, I’ve learned which is the right choice, so we hopped in the car and headed down the road to the craft store.

View Story


Tim’s Takeaways: What More Do We Need to Know?


Although it’s been more years than I care to admit, I still remember very clearly the class on careers that I was required to take in junior high school. On a table in the front of the class were several boxes filled with all sorts of different job cards that a student would search through to learn about different professions. Each card listed the schooling and experience required for that particular job, its expected responsibilities and duties, and an estimated salary. Our assignment was to choose a handful of these cards that interested us, study them, and then list the reasons why we would or wouldn’t pursue those jobs as a career. As you might have guessed, I blew the assignment.

View Story

Tim’s Takeaways: Success Begins With a Little Confidence


Bruno Gaido was a young radioman-gunner portrayed by Nick Jonas in the 2019 movie “Midway.” An early scene shows a Japanese bomber trying to sink the USS Enterprise by crashing into it with his plane. The scene shows the bravery of Bruno as he ran across the deck of the ship and jumped into the rear seat of a parked airplane, using its guns to shoot back. His shooting damaged the bomber just enough to force it off course, thereby saving the ship just as the bomber crashed into the Bruno’s plane, cutting the plane in half and made it spin around. We can learn a lot from the confidence of Bruno Gaido.

View Story

Tim’s Takeaways: Manufacturing Documentation—Keep the Builder in Mind


It was the end of May, which among other things, meant that the Major League Baseball season was once again in full swing (pun intended). While my wife was happily settled into the couch with her Seattle Mariners cap, T-shirt, blanket, and coffee mug cheering on J.P Crawford and the rest of the team, I re-watched “Field of Dreams,” and was again mesmerized by the voice that speaks to Kevin Costner’s character: “If you build it, they will come.” As circuit board designers, it’s probably not all that unusual to hear similar voices speaking to us, especially after staring at a layout for hours, and hours, and hours. But in our case, the message is typically a little different, and sounds more like, “If you document it correctly, they will build it.”

View Story

Tim's Takeaways: Today's Preparations for Tomorrow's PCB Designs


What skills actually prepare you for your future career? Tim Haag reflects back on an eighth grade typing class that baffled those around him because "everyone knew that I had absolutely no aptitude for any sort of literary or language skills." Yet, despite his atrocious spelling skills, Tim excelled in typing and those newly-honed skills served him well as he began to learn about laying out circuit boards on various computer design systems. It was one random decision amongst so many others. What was it for you?

View Story

Tim's Takeaways: Gremlin Avoidance Tactics to Improve Productivity


Sometimes I am really envious of those who work with steel, on a construction site, or even tilling the earth. All of these are tangible activities; you mold the steel, or build a house, or harvest a crop. Instead, I work in electronics. Most of the time it is a good life, but every now and then a nasty little gremlin will pop up its ugly head and mock you. It could be a circuit that just won’t give you the performance that you need, a short that you can’t find, or worst of all, an intermittent problem that just won’t go away.

View Story

Tim's Takeaways: The Misadventures of High Voltage and Other Related Problems with Power


If you’ve read my column before you know how much of a fan I am of aviation, especially when it comes to older airplanes. You can imagine how ecstatic I was when 11 years ago my wife gave me the greatest gift of all; a half-hour ride on a fully restored WWII B-17 Flying Fortress. This plane was the real deal folks. A four-engine heavy bomber stuffed with gun turrets, narrow and cramped crew areas, and the cold hard metal of unforgiving hardware that could give you a serious bruise on the forehead if you weren’t paying attention. From wingtip to wingtip, the “Liberty Belle” was saturated with a rich ambiance of history that emanated from every one of her nearly 400,000 rivets that held this aircraft together.

View Story


Tim's Takeaways: Say ‘No’ to File Hoarding: Data Management Tips


There are a lot of different types of “collections” in life that need managing, and like my proliferating pile of tax paper publications, they all need their own eloquent solutions to keep from getting out of control. Take for instance the amount of data that is generated during the design of electronics. The first thing to consider in our world of PCB design is just how much data there is that needs to be managed. From a casual overview it may not seem that extensive, but let’s break the average design down into its four separate pieces. This gives us the schematic, circuit simulation, PCB layout, and analysis, and that is just a generalization. Designs often have more pieces than that in them, especially when you consider the depth of system level design.

View Story

Tim's Takeaways: The Collaborative PCB Design Process—A Necessity for Efficient Manufacturing


Circuit board design used to be a more complicated and lengthy process than it is now with the need to build scores of test circuits, develop multiple prototypes, and toiling with manual design operations. The one good thing about all of this time was that it gave ample opportunity for everyone to be involved.

View Story

Tim's Takeaways: Some Timely Advice


Who inspires you to be a better designer? For Tim Haag, he finds motivation in the story of Bert Christman. Read on for how this daring Navy pilot's life relates to advice in the world of circuit board design.

View Story

Tim's Takeaways: DDR Routing, and Other Big Fish in the Lake of Technology


Tim's fishing story relates well to designing circuit boards. Intrigued? Read on, he explains how "there's always a bigger fish."

View Story

Tim’s Takeaways: Conquering Layers of Challenges in PCB Stackups


When he first started laying out printed circuit boards many years ago, Tim was working for a computer systems manufacturer whose PCB designs were all multilayer boards. While there were a great many things that I learned during my time working there, it also fostered one bad habit; He became accustomed to relying on being able to use multiple layers for routing instead of planning a more efficient layout. Here, he breaks it all down.

View Story


Tim’s Takeaways: PCB Vias, ‘You Have a Go’


Do you remember the old TV show “Stargate SG-1?” With the exhortation of “SG-1, you have a go” from their commanding officer, the stargate would instantaneously transport an intrepid band of heroes to new and exciting locations each week. Tim Haag details his realization that the stargate is nothing more than a giant via in space!

View Story

Tim’s Takeaways: Thermal Management for PCB Designers—Staying Out of the Fire


If there’s one thing in life that really feels the pressure of being in the hot seat, it’s the PCBs that we design. But PCB designers often feel a lot of pressure while doing their work, which puts them squarely in the hot seat. Tim Haag shares four techniques in thermal management for PCB designers.

View Story

Tim's Takeaways: Navigating Industry Expectations


While some expectations are normal—and, well, expected—in the workplace, there are also those that do more harm than good. Tim Haag unpacks negative expectations and shares suggestions for improving communication in the workplace, as well as positive expectations that you can set for yourself.

View Story

Tim’s Takeaways: Working From Home—5 Tips for Newbies


Due to the COVID-19 outbreak, many people who have worked in an office environment for their entire career have suddenly found themselves shifted to working remotely. At first, this may seem like it isn’t that big of a change, but it may be a bigger deal than you realize. Tim Haag, who has worked from home for over 17 years, shares five tips for making the most of this situation and working successfully from home.

View Story

Tim’s Takeaways: Clearing Up the Buzz


My first “real” job in the world of electronics was working at a Radio Shack store back in the late ‘70s. It was a step up from flipping burgers, but it didn’t last long. However, there was one notable aspect of that job; I was there during the time that Radio Shack introduced its first personal computer—the TRS-80. Although it is practically unimaginable now, in those days, there wasn’t much in the way of personal computing available for the general consumer.

View Story


Tim's Takeaways: Realizing a Higher Standard for PCB Design


To the untrained eye, one circuit board may look pretty much like any other, but as we know, there are major differences between them. Not only are they different in purpose and design but also in how they are manufactured for specific industries. If you are designing medical equipment, for instance, you will have to meet many different regulatory requirements from organizations, such as the Food and Drug Administration (FDA), World Health Organization (WHO), and International Electrotechnical Commission (IEC), among others.

View Story

Tim's Takeaways: Clear Communication Takes the Cake


Whether baking a cake or building a circuit board, it’s all about clear communication. If the person writing the recipe had not made the choice to clearly communicate what their intentions were for baking that cake, I would have been lost. A missing ingredient here or an incorrect oven temperature there and my birthday surprise would have ended up in the garbage in the same way a successfully built circuit board starts with clear communication from the designer. Circuit board manufacturers want to create a perfect PCB for you, but they can only do so to the extent of the instructions that you give them.

View Story

Tim's Takeaways: Rules Keep You from Crossing the Line


Driving rules are designed to keep drivers between the lines of traffic instead of crossing over those lines into dangerous situations. Similarly, design rules are also intended to keep PCB trace routing between the lines instead of crossing over them as well. But you might be surprised how many people refuse to use the full potential of their DRCs to protect themselves, and in some cases, refuse to use them at all.

View Story

Tim's Takeaways: I Think I’ll Go for a Walk


Many years ago, my boss at a PCB design service bureau had his own unique way of encouraging us to take a break. He would come through the design bay and call out in his deep baritone voice, “DARTS!” and we would all follow him into the break area for a quick game. In addition to the benefits of taking a break, forcing our eyes to focus in and out as we threw a dart was a great way to relieve us all from the eye strain of older CRT monitors.

View Story

Tim's Takeaways: A Job Worth Doing


I get it. We PCB designers are made of the kind of tough stuff where we will work ourselves to death if given the chance. But in our all of our efforts, are we really doing it right, or could we somehow be doing it better? Let’s take a moment to consider some other ways that we might help ourselves to improve.

View Story
Copyright © 2023 I-Connect007 | IPC Publishing Group Inc. All rights reserved.