CEO Interview with Joel Jorgensen of FlowAccel

Joel Jorgensen founded FlowAccel, helping silicon systems engineering leaders deliver on roadmap commitments and scale development organizations. During 25 years at Intel, he spent 15 years in analog design and architecture for non-volatile memory technologies, earning two patents and co-authoring two IEEE ISSCC papers. He also served as an NPI Chair in manufacturing and later led efforts to expand the use of Steven Spear’s High Velocity Edge methodology beyond Intel’s SSD organization, including bringing Spear in to work directly with Intel engineering leadership.

Tell us about your company?

FlowAccel helps silicon systems engineering leaders deliver what they committed to deliver.

Over 25 years at Intel, as a designer, architect, NPI chair, and later leading development flow design and improvement, I watched great engineers lose weeks to handoffs, rework, and workarounds that had nothing to do with the technology.

Development is hard enough without the work system working against you.

Schedule pressure and complexity aren’t going away. I believe we can have both: a thriving business and a life outside of work. That is my quest.

What problems are you solving?

Every organization starts from a different place. Some want to go faster. Some need to scale. Some need to do more with the people they have. The method is the same, the problems change.

What they have in common is time lost between the milestones. Handoffs that stall. Validation cycles that run longer than they need to. Workarounds everyone knows about and nobody owns. Teams treat these as technical problems and throw more engineering at them. They’re workflow problems.

One example from my own career: a program was a month late on a five-week tape-in schedule. We cut post-silicon validation cycle time 50% across ten steppings and recovered it.

I’m an engineer, so I love solving problems. The bigger, gnarlier, and faster-moving, the better.

What application areas are your strongest?

Silicon systems product development. I’ve worked across the product life cycle, from front-end requirements through back-end manufacturing, at the device and platform level.

I started as an analog circuit designer, became a flash memory architect with two patents and two ISSCC papers, and introduced new products into a fab. For the last eight years I focused on accelerating our product life cycle and scaling engineering operations to scale the business. That work delivered a $400M per year labor-hour savings opportunity and trained 1,700 people in workflow design.

What keeps your customers up at night?

Survival. In this industry, usually only the top few companies are profitable. Times are good right now, but nobody gets to focus only on today. You have to deliver this roadmap while preparing for the next one.

VPs worry about delivering the roadmap. Directors carry the same pressure at the program level. Complexity keeps growing, change keeps speeding up, and the competition is relentless. The market can change on a dime, and you have to adapt wherever it goes. Once a business matures, the expectation is more output, faster, without adding headcount.

Now AI is changing how products get built. It will speed up change and be disruptive until we figure out how to use it well.

There is no downtime in this industry. There’s always more work than can be done. Leaders have to sort through all of it and keep their teams focused on the right things.

What does the competitive landscape look like and how do you differentiate?

Leaders have options. Large consulting firms. Agile and transformation coaches. Tool vendors. Adding headcount. Most of those come from the top down with a canned model, an org chart, or a transformation program. There are no one-size-fits-all solutions that stick.

I’m an engineer who lived product development from the inside for 25 years, from a lot of different seats. Before semiconductors, I ran my own businesses and our family farm. All of that shapes how I see a problem.

I start where the work happens. I spend time with the engineers, see how they actually work, and learn what’s getting in their way. Then I work with the leaders to understand where they need to go. The path forward comes from connecting the two.

Knowledge and information flow through a development organization like current through a circuit. Milestones are the registers. The work between them is the logic. If that logic is poorly designed, your program slips, no matter how good your engineers are. So I design work like engineers design products. Same method, different content: define the problem, understand the work, redesign the work, and achieve the outcome. That’s how you win between the milestones.

The payoff is twofold. Leaders deliver what they committed to, and their teams spend fewer nights and weekends fighting the system. There is nothing better than seeing an engineer’s eyes light up when they finally see the problem that’s been torturing them for years.

What new features/technology are you working on?

Faster ways to see the work. Mapping a development flow has always taken a lot of engineering time: interviews, workshops, whiteboards. AI changes that. Teams can capture what they know and how they actually work with far less effort. I’m testing different ways to do that, so we get to the real bottleneck sooner and engineers spend their time solving problems instead of documenting them.

How do customers normally engage with your company?

It always starts with a conversation about their challenges. First, I want to make sure I can help. Then it comes down to what kind of help they want. I can coach their team through it, lead it with them, or some combination of those. If it isn’t a good fit, I’ll help them find someone who is.

Call me at 916-836-9272, use the contact form on my website, email joel@flow-accel.com, or message me on LinkedIn. Whatever you’re most comfortable with.

Also Read:

CEO Interview with Vivek Raghuraman of Mixx Technologies

CEO Interview with Dr. Stefan Pastine of Thintronics

CEO Interview With Nick Kurayev of ScienceSoft

Share this post via:

• 
• 
• 
•