3 Lessons in Building From the Managing Director of Garmin Canada ⚙️🏃🏻♂️➡️
A recap of October 23rd's Calgary Tech Thursday's session on the Garmin Canada story with Jim Rooney
Last week’s Tech Thursday session, co-hosted by Garmin, was a fireside chat with Garmin Canada’s Managing Director, Jim Rooney in front of a capacity audience.
This is our recap of the top ideas from our Fireside Chat with Jim Rooney of Garmin Canada.
“The origins of that [Garmin’s technology] were scratched on whiteboards in my garage.”
Jim Rooney, Managing Director, Garmin Canada
Missed this one? Check out our recap videos on YouTube and be sure to follow us on Instagram for updates on everything Tech Thursday.
TL;DR
Find a Pain Point; Solve It: Solving problems when building products should be focus #1; don’t force yourself to create customers, provide solutions to pain points that already exist.
Failure is Always a Part of Success: Failure when building is not a death sentence, in fact, within major companies worldwide, stories of trying, failing, and trying again are frequent.
Patience is Key; Success Isn’t Always Instant: Expectations and instant gratification can be dangerous when building; being confident about any product/business is key to staying the course if early returns are not what was initially expected.
3 Lessons in Building From Jim Rooney of Garmin Canada:
1. Find a Pain Point; Solve It
Ensuring you are building something that is actively solving a pain point is crucial in the success of any product. As Jim mentioned, prior to taking the leap and building a product for runners to track their distances, there was no alternative. Solving that pain point that most didn’t realize they had (more on that later) was the key to Jim and Garmin’s success.
Why this is important:
A consistent theme throughout 2025’s Tech Thursday panels has been the focus on building with the intention of solving problems. Whether shared by Jim Rooney with Garmin or Jeff Smith with Digital Commerce Bank, it is of the utmost importance that a problem is being solved when building a product/company, otherwise the long-term feasibility of said product/company is significantly reduced.
Key Takeaway: Solving problems when building products should be focus #1; don’t force yourself to create customers, provide solutions to pain points that already exist.
2. Failure is Always a Part of Success
While there are hundreds of quotes speaking about the importance of failure in any successes, contextualizing those sayings within a success story, especially with a company as successful as Garmin, helps to reiterate the meaning behind those sayings. Jim’s story of an early test involving wires connected to a fanny pack eventually failing in spectacular fashion serves as a poignant reminder of how even the most successful companies have many stories of failure.
Why this is important:
Treating failure as a step to success as opposed to an indicator that a product/business is destined to fail is key in both innovating and growing in any industry. Within any successful company, founders, executives, and employees alike have stories of trying and failing, and the more failure is viewed as a part of the journey to success, the more innovation and creativity will flourish.
Key Takeaway: Failure when building is not a death sentence, in fact, within major companies worldwide, stories of trying, failing, and trying again are frequent.
3. Patience is Key; Success Isn’t Always Instant
Success isn’t instant, regardless of how great a product may be or how big of a problem is being solved. As Jim reflected on, everyone who used his initial product was a huge fan, and adding Nike as a customer to the already positive feedback made it easy to assume things were going to take off, though that ended up not being the case. Jim’s experience helped provide an example of how important patience is in business, and that seeing things through, especially with positive indicators, is vital.
Why this is important:
In an innovation environment, patience can be fleeting, further emphasizing the importance of this example with a successful company like Garmin. Despite an acclaimed product and customers like Nike, it was a slower pick-up in the market; but patience paid off, and Garmin is what we now know it in the market today.
Key Takeaway: Expectations and instant gratification can be dangerous when building; being confident about any product/business is key to staying the course if early returns are not what was initially expected.
Hot Takes: Not All Acquisitions Look the Same
Jim’s description of how the Garmin acquisition took place and his surprise at what was expected (or the expectation to keep doing what they were doing) served to show how different acquisitions can be across industries and companies. It served as a great reminder that while previous acquisitions can be helpful in visualization of what the process might look like, each one is unique.
Why does that matter? Looking to other acquisitions shouldn’t be used as a blueprint for future acquisitions as each one is different (and occasionally, surprising).
Don’t Miss Our Next Events!
November 13th: ‘Federal Budget Review: What Impact will it have on Tech & AI’
Co-Host: Crestview
Including:
Bridget Howe, VP at Crestview and Liberal Commentator
Evan Menzies, VP at Crestview and Conservative Commentator
Moderated by: Philippe Burns, Co-Founder at Tech Thursday
November 13th: Hackathon - Solving the Canadian Productivity Crisis - Calgary
In Partnership With: Neo, Helcim, ZayZoon, Microsoft, Motiv, and Robin