Bryan Scott McMillan

Please introduce your professional background and describe the leadership roles you’ve held throughout your career.

I spent more than 30 years in the medical device industry in senior executive and advisory roles. My work covered operations, sales, marketing, strategic partnerships, product launches, regulatory planning, and business transformation. I was often brought into situations where teams had stalled or businesses were losing momentum. My role was usually to simplify problems, align teams, and rebuild trust across departments.

A large part of my career involved helping organisations move through change without creating chaos. I learned early that leadership is less about authority and more about consistency. If people trust your process, they will usually trust your direction.

What business model shaped the way you operated as an executive leader in the medical device industry?

Most organisations I worked with used a hybrid model. Core strategy, leadership, regulatory oversight, and relationship management stayed in-house. Manufacturing, specialised engineering support, and some operational functions were often handled through external partners.

That structure only works when communication is disciplined. In regulated industries, weak coordination creates delays very quickly. I spent a lot of time building systems that reduced confusion between internal teams and outside vendors.

I always believed the closer people stayed to the actual problem, the faster good decisions happened.

How did you differentiate yourself as a leader in a highly competitive industry?

I listened longer than most people expected. A lot of executives walk into a struggling environment and start making fast changes. I usually spent the first few months asking questions.

One thing I learned is that most operational problems are communication problems wearing different clothes. Teams often already know the solution. They just stop feeling safe enough to say it out loud.

I also stayed calm during pressure. In medical devices, panic creates mistakes. Teams need steadiness more than speeches.

What sectors and areas of business did you focus on most throughout your career?

My primary focus was medical devices and healthcare operations. Over time, that expanded into strategic advisory work, leadership development, and organisational restructuring.

Earlier in my career, the focus was heavily operational. Product launches. Regulatory coordination. Scaling teams. Later, more of my work centered on helping organisations rebuild alignment during periods of rapid growth or internal strain.

After personal loss shifted my priorities, I also became deeply involved in nonprofit and grief-support work.

What were the most common challenges companies brought you in to solve?

Usually three things. Operational breakdowns. Team misalignment. Or stalled growth.

Sometimes companies moved too fast and lost structure. Other times they became too cautious and stopped innovating. Most situations required simplifying systems and restoring trust between leadership and staff.

One recurring issue was meeting overload. Teams were spending more time reporting work than doing work. Reducing friction often solved more problems than adding new strategy.

How did you stay ahead of industry shifts in a fast-moving field like medical devices?

I stayed close to operators. Engineers. Regulatory teams. Sales staff. Those people usually see problems before leadership dashboards do.

I also protected thinking time. Quiet walks helped me process information better than constant meetings ever did. Some of my clearest decisions came while walking without headphones.

I never believed leadership should chase every trend. Most trends disappear. Strong systems last.

Did you work with the same organisations repeatedly during your career? What built that long-term trust?

Yes. A large percentage of relationships became long-term. Trust usually came from consistency and honesty.

I tried to avoid overpromising. If something would take longer, I said it directly. If a launch was not ready, I said so even when people disliked hearing it.

One executive later told me, “You were the first person who didn’t try to sell confidence before solving the problem.” That stayed with me.

How did you measure operational success and team performance?

I focused on clarity more than volume. Activity alone means very little.

I looked at execution quality, decision speed, turnover, communication patterns, and whether teams trusted each other. If a company hit targets while burning people out, I considered that a weak system.

Healthy teams solve problems faster because they are not wasting energy protecting themselves internally.

How did you support teams after major launches or operational projects?

Post-project recovery mattered a lot to me. Many companies celebrate deadlines and ignore exhaustion afterward.

I tried to build decompression periods into major cycles. Fewer meetings. More direct communication. Honest review sessions about what worked and what failed.

Teams need recovery if you expect long-term performance.

What pricing or business structures were most common in your executive and advisory work?

Most of my work happened inside executive leadership roles, so pricing structures were usually organisational budgets rather than outside consulting fees.

In advisory work later on, structures varied depending on project scope and duration. Some were fixed engagements. Others were milestone-based.

I generally avoided projects where expectations were unclear from the beginning.

Did you ever turn down opportunities based on fit or scope?

Yes. Usually because of culture, not budget.

If leadership wanted speed without accountability, it rarely ended well. I learned that early.

I also avoided environments where teams were afraid to speak honestly. Fear slows everything down.

What major challenges shaped your career most?

Losing my wife to cancer changed everything. It forced me to rethink success, pace, and leadership.

Professionally, one of the hardest lessons came from pushing a product launch too quickly early in my career. I ignored concerns from the regulatory team because I felt pressure to move faster. The launch stalled.

That experience permanently changed how I make decisions. Urgency is not strategy.

How did you encourage innovation inside large organisations?

I tried to reduce fear around mistakes. Innovation slows down when people feel punished for imperfect ideas.

I also encouraged junior employees to speak first during meetings. Younger team members often had the clearest view of broken systems.

Innovation usually improves when ego decreases.

What role did culture play in the teams you led?

Culture shaped everything. Most operational problems were cultural problems underneath.

I tried to build environments where people could disagree without punishment. Once trust improves, execution improves quickly afterward.

Culture is not slogans on walls. It is behavior repeated consistently.

What kind of long-term impact did you want your leadership to create?

I wanted to leave organisations healthier than I found them. Better communication. Better systems. Better trust.

Now that I spend more time in nonprofit and grief-support work, the goal feels similar. Remove friction. Help people move forward more clearly.

How has your leadership style evolved over time?

Earlier in my career, I thought leadership meant solving problems quickly. Over time, I learned it often means slowing down enough to understand them properly.

I lead calmer now. I ask more questions. I react slower.

That change made me more effective.

What advice would you give future executives and leaders?

Protect clarity. Protect trust. Protect your energy.

Most leaders burn themselves out trying to look certain all the time. Good leadership is usually quieter than people think.

The best decision-makers I met were rarely the loudest people in the room.