Four important lessons gleaned over a three-decade design career.

There’s an old saying among test pilots: “Any landing that you can walk away from is a good landing.” They also know that there are old pilots, there are bold pilots, but no old, bold pilots – or so the saying goes. If you want to hang around as a PCB designer, you can only hope to walk away from your mistakes with your career intact. So, this is a chance to learn from my mistakes from 35 years of design work.

Going all the way back to the ’90s finds me in my first PCB design role. I had just taken an internal transfer to the commercial side of the business after a couple of years of feeding from the government trough. My manager on the mil-spec side, Merrill, was a father of a dozen children and was an all-around nice guy, perhaps a bit of a pushover.

Before applying for the transfer, I wanted to talk with Merrill, so I came up behind him and asked if he wanted to go to Armadillo Willy’s, a local barbecue place, for lunch. I didn’t see that he had a sandwich in his hand and was about to take the first bite. Instead, the sandwich hit the desk with a thunk, and we were off to the restaurant. Such was his dedication to his people.

Figure 1. A multilayer control board for RF amplifiers circa 1999. By that time, I had done many of these and could turn them around quickly.

A little background: A recent audit from the Army had raised many concerns. I was fresh out of a six-month program at the Copper Connection, a local PCB/CAD trade school that taught the Department of Defense drawing standards along with AutoCAD. I knew my stuff well enough that one of our mechanical engineers asked me if I had a photographic memory. No, I had just put in the six months to study the Drawing Requirements Manual.

My drawings were cleanest among the several CAD designers, with only two flags on my drawing package. One was about hardware callouts. I was labeling threaded holes with a commercial designation. So I called out a 4-40 UNC-2B threaded hole when it should have been 0.112-40 UNC-2B. That leading “4” was the same issue we all had where the auditors wanted a diameter value instead. That was an easy one.

1. Assembly drawings do not tell you how, only what. The other issue was with what the auditors called “methodized drawings.” At the time, Merrill asked me what that meant. My reply was to mention the design reviews where the manufacturing engineer would request a list of notes to add to the assembly drawings. The intention was to have a single document that the assemblers could use to place components. I reminded Merrill of all the times I had pushed back on those requests but was overruled. Lesson learned.

The noble idea was to keep assembly workspaces tidy. It also made the drawings (what is) into a procedure (how to). The government has reasons to avoid entangling the two.

The outcome of that audit was that, from that day on, I was tasked with checking everyone’s drawings for compliance with the manual. I had already spent time doing quality control inspection of PCBAs on the assembly line and eventually bare PCBs in the receiving inspection lab. This checker distraction is going to cut into my productivity!

Even before looking at the first drawing, I knew this would be a thankless job. As the newest, most junior person, I wasn’t going to endear myself to anyone by nitpicking their work. So, in the end, that decision to put my name in the Checked By box was a wedge that had me looking over the cubicle wall toward the other team that was enabling 3G wireless technology for the masses.

Figure 2. My idea of what makes up an appropriate list of notes. Any instructions on the assembly drawing should be verifiable by checking the condition of the PCBA. How would we know, for instance, if the assembler used its ESD strap and ionizer while doing the job?

Looking back, I should have brought my Drawing Requirements Manual to the design review and bookmarked the section about drawings vs. procedures for reference. Having solid facts from a reliable source is better than “just my opinion.” Now, we have the internet, where getting that kind of information is trivial.

Merrill was unable to talk me out of applying for the transfer, though he tried. My new manager, Ed, approved and I moved to the other side of the building. As an aside, the new job was doing multilayer boards, where everything on the DoD side was single-sided power amplifier boards. The control boards were always outsourced from either side. That was about to change, and I was going to be the one to make it so.

2. Crowding components is bad no matter whose idea it is. My buddy Joe warned me that “Ed don’t take no sh*t,” and I was like, “Why should he?” Then he relayed that when Ed was asked what would happen if I could not design multilayer boards, his reply was, “Then I’ll fire him.” Right there is a useful data point. After three days of training on some actual PCB design software, I was cut loose on my first four-layer job. I taped out four layers, no mask, no silk, no clue! That all came together on my second control board.

The commercial group was growing and hired a big-brain kind of guy named Dave for that second board. Note that Dave was eventually promoted to VP of engineering. He had a persuasive nature and convinced me that two resistors had to be super close or the PLL circuit would not work. I wanted it to work, so I nudged them closer and closer until Dave said, “That’s good.”

Dave was wrong, and by listening to him, I was also wrong. I’ve told this part of the story before, so it may seem familiar. Ed calls me into his carpeted office and tells me to shut the door and sit down. It went something like this.

Ed: Manufacturing is reporting solder issues with a couple of parts on your board. Do you know that we need a solder dam between every pin?

Me: Um, yes.

Ed: So, why do these two parts have their pads too close for that?

Me: Oh, Dave told me that is necessary for the PLL …

Ed: (cutting me off) If I want Dave to design the board, then I don’t need you. These boards have to be manufacturable or there’s no point.

Me: *Gulp* OK.

Ed: Alright, go back to work but don’t ever do this again.

At least I kept my job for another eight years. And that never happened again. Not at that first job, nor any subsequent job over the following three decades. Working for startups is all I did until Qualcomm bought one of them. That is where big company processes (and politics) come into play.

3. Learning big company politics the hard way. I was having a hard time getting guidance on shield footprint standards. I had hit up the San Diego-based manager of the mechanical engineering team hoping to learn more. Enough time had passed that I sent a second message letting her know that I was feeling left out about the lack of feedback.

That message totally backfired. It was something I picked up in a course called Managerial Interpersonal Effectiveness (MGMT101). We were instructed not to use a “You” message but rather an “I” message to let the other party know how their behavior is affecting you. That mechanical engineering manager “schooled” me on etiquette and bcc’d my manager. Yep, another call to the carpet when a simple phone call may have done the trick. I did not see that one coming.

Figure 3. A PCIe-based MIMO radio PCB featuring a multi-chamber EMI shield

Following that incident, a lot of good things came out of working six years for Qualcomm. One was that they had an exceptional offshore PCB vendor. I’ll name names. It was Plotech. They had the chops to deliver on smartphone-grade PCBs. They were, at that time, a top 100 global PCB vendor but far enough down the list that they were not monopolized by one of the mega-players in the industry. They would treat us well even though Qualcomm was only doing pilot programs to generate reference designs.

4. Using a Taiwan-based vendor without understanding customs processes. My next opportunity was at Google’s Chrome OS hardware team. Not long after arriving, the procurement person moved to a different division. We were told to do our own purchasing until the role was filled. I had a radio board that would be perfect for Plotech, so I contacted them to save some money over what the local shops would charge. Even though my email ended with @google, they asked if my company had a website to see if we were legit. Yeah, you might have heard of us!

So, we set up a nondisclosure agreement and I got the quote and ordered a batch of bare boards. I circled back to them a few days after the boards were supposed to ship to get a status on the order. That’s when I learned about customs. You have to lay the groundwork before you can import electronics to the US. In hindsight, a local vendor would have been just fine; it’s not like the company didn’t have the money to spend. That cost the development team about a week where a one-day slip is still a failure.

A bonus mistake that I could walk away from was the time I did a favor for a coworker by cleaning up the reference designators for the silkscreen and the assembly drawing. I pulled the design from the repo and wrote a script while I organized the text, and then pushed my script to the repo so he could straighten it all out by repeating my work on his database.

Well, the find filter had changed between my pulling and pushing, and instead of moving the text, it moved almost every part on the board. He had the “stretch” command going, so it also contorted the traces while it was at it. Of course, he saved first, but we let it run its course so we didn’t hang up the license server. It was a good time to go get some of that free food, although watching it destroy the layout was hilarious!

This could easily have been five or 10 problems I’ve caused. The general idea is that communication is important. If you’re uncomfortable with something, share your discomfort, but don’t surface a problem without offering a solution or two. Circle back with the team early and often to make sure you stay on track. Educate yourself on what the vendors can and can’t do. Use nice words in case you must eat them later. This all should be part of your nature if you like doing PCB design.

John Burkhert Jr. is a career PCB designer experienced in military, telecom, consumer hardware and, lately, the automotive industry. Originally, he was an RF specialist but is compelled to flip the bit now and then to fill the need for high-speed digital design. He enjoys playing bass and racing bikes when he’s not writing about or performing PCB layout. His column is produced by Cadence Design Systems and runs monthly.