Recent thoughts

The Pivot From Pixels to Product

“Pivot”. Ugh. Business jargon. I know, I know… but here we are. After years of working “on the business side” of product, I’ve often wondered if I sold out.

I realized early, while still in design school, that I was a good but not great designer; at the time I was a far better front-end Web developer than designer, and I never imagined given my background that I had a future in business.

Those were the days of late-night Photoshop marathons and the thrill of getting both Internet Explorer and Firefox to render pixel-perfect CSS layouts the same way (finally). I used to obsess over the little things: kerning, grid alignment, and how to write code as beautiful as the website design itself. Craftsmanship was important to me. I loved the game.

I didn’t know what a “product manager” was then and, as far as I can tell, “Product Manager” as we know the role today only really became a thing sometime around 2007. Fast-forward to 2012 and I accepted my first “Product Manager” job after growing tired of taking orders from others (here’s the roadmap, do it) and hitting a salary plateau. I really accepted the job for the wrong reasons: the promise of power and money.

Truth be told, product management roles do generally deliver on these promises. Product managers are well paid, and the role inherently gives you a certain amount of “power” (to “decide” what other people will work on). But with great power comes great responsibility—responsibility to your clients, your colleagues, and yourself. The multitude of articles about communication, collaboration, and empathy being essential for excelling as a product manager in 2025 are 100% correct.

Here’s the twist: these qualities are often ingrained in a designer’s very essence. Turns out, the talent and passion that led me to study design, and the soft skills I learned as a working as a Web developer, were actually my superpowers all along.

During these early days of my career I learned to listen closely to clients, understand their needs, and translate abstract ideas into tangible solutions. I learned how to collaborate with developers and marketers, to bridge gaps, and to speak everyone’s language. And most importantly, I learned empathy—not just for users, but for the people I worked with every day.

Now, as someone leading product teams, I believe having a design background is more than just an asset—it’s a secret weapon. So much of product management comes down to advocating for the user and ensuring that functionality doesn’t overshadow usability. Designers bring a unique perspective to the table. We’re trained to see both the forest and the trees, to balance aesthetics with functionality, and to bridge the gap between what users want and what’s possible to build.

Reinventing yourself is challenging, but in today’s job market, it’s increasingly essential to do so regularly. If you’re a designer who has been thinking of moving into product management at all now is a great time to expand your job search. Don’t forget…

  • User-centric thinking is your superpower – As a designer, you live and breathe the user experience. You think about flow, friction points, and the emotional response a user will have to what you create. When I prioritize features or debate trade-offs, I’m always asking, “How does this impact the user?” A well-designed product isn’t just functional; it’s intuitive, empowering, and enjoyable.
  • Storytelling gives you a strategic advantage – Good design tells a story, and as a designer, you’re constantly pitching ideas to clients or stakeholders. This skill translates seamlessly to product management. Whether I’m presenting a roadmap or advocating for a new feature, I know how to frame ideas in a way that resonates. The difference now is that my “designs” are product strategies. The colors and typography have been swapped for charts and user feedback, but the goal is the same: craft something compelling that aligns with both the user’s needs and the company’s goals.
  • Constraints are nothing new to you – Designers are used to tight deadlines, limited budgets, and navigating tricky feedback. That ability to thrive within boundaries prepared me for the balancing act of product management, where every decision involves trade-offs. Sometimes, you can’t build everything you want, and that’s okay. Just like I once turned a client’s “meh” feedback into a final website I was proud of (that met their needs), I now find creative ways to prioritize features and deliver value, even with limited resources.

The leap from designer to product manager might not be the most common career path, but for me, it was the perfect fit. I still get to solve problems, collaborate with talented people, and create things that make life easier (and maybe a little more delightful) for others.

Looking back now I realize that I didn’t sell out—I leveled up. Product management wasn’t about abandoning my values and design principles for power or profit. It was about expanding them into new territory, applying the same obsession with detail and craft to entire products, teams, and strategies. And for designers considering a similar shift, let me tell you: you’ve already got the skills and experience to be a product manager—you just need to reframe them.

Let’s Get Dirty and Make the Web Weird Again

If you’re reading this you’ve found the new dansauve.com (which I refer to as DSDC because it sounds cool), and holy hell, does it ever feel good to be back. I’ve had this domain name since 2003 and have used it primarily for email hosting, with a few simple resume/portfolio sites coming and going over the years, but it’s been over 20 years since I’ve had a proper blog. Twenty years! I had honestly forgotten how the hours melt away while setting up a site, designing a thing for fun, tweaking CSS, and bringing it to life in a web browser. Relaunching DSDC this past holiday season has been like catching up with an old friend I didn’t realize I’d missed so much.

I owe the inspiration for this to my job. I started working at WHC last year, and for the first time in too long I’m doing something I genuinely enjoy. It’s web hosting—something I’ve always been passionate about (anyone remember the VC200?). It’s funny how life works; you find yourself in a job you don’t hate, surrounded by people who care about the same stuff you do, and suddenly you’re itching to create again. This blog is part of that. It’s my way of getting back to my roots.

The design? It’s a relic from 2007—a never-launched design for a tumblelog I had at the time called Bleached Blue. I dug it out of the archives, dusted it off, and brought it back to life. Most of the HTML and CSS is exactly as it was 15 years ago. Isn’t that wild? It all still works, no problem. Back then, I was a big fan of ExpressionEngine; I even had the integration ready to go. But for some reason, it never got finished. I’m glad it didn’t because now it gets to live here.

What I love about this design is that it’s clean but gritty, with just enough rough edges to keep it interesting. It’s got a bit of that old school charm I miss so much from the late 90s and early 2000s—the era when when David Carson‘s designs in Ray Gun made typography exciting and getting my hands on an issue of Emigre was like a wet dream. When you just had to see what 2Advanced had put online (I didn’t even realize they were still around!). When flipping through the skate mags I read at the time like Daily Bread (yeah, yeah… I was an aggressive inline skater because at 18 I already felt “too old to learn how to skateboard) was as much about soaking in the gritty, rebellious layouts and bold typography as it was marveling at the perfectly captured tricks. When I got accepted into the Swankarmy and met strangers online who thought I had potential, one of them even sent me a CD in the mail with Adobe PhotoShop (which led to me going to design school). Back then, design and the Web were exciting. Experimental. Weird. Now everything looks and feels the same. Every website is polished and sterile, like they’re all scared to have a personality. Screw that.

Selections from the "portfolio" I submitted with my application to design school
Web design samples from the portfolio I submitted with my design school application. This is what design-focused personal websites looked like in 1999.

Nick Hamze nailed it in his recent post on the WordPress blog: WordPress themes need more weird. Fuck yeah, Nick. A huge chunk of the Web runs on WordPress and web design needs more weird. It needs more risk. We’ve spent too long designing for approval—making everything mobile-first, app-like, and “on brand.” What happened to making something because it’s cool? Because it’s fun? I miss the days when you’d stumble across a random person’s site—Paul’s Website About Sea Turtles or whatever—and it was exactly what it claimed to be. Pure passion, informative and entertaining, no bullshit.

The Internet used to feel like a sprawling labyrinth of people’s creativity. Now it feels like walking through a mall where every store is trying to sell you the same beige sweater. Google is a mess, Wikipedia is great but clinical, and social media? It’s just people shouting into the void for likes. Even most mobile apps these days seem to be designed as soulless utilities that are functional but utterly forgettable. Everything feels like the same flat, sterile interface, optimized for metrics instead of delight—like we traded creativity for conformity somewhere along the way. Where’s the heart? Where’s the weird shit?

I don’t want this blog to play it safe or be predictable. I want it to feel like the Web used to: messy, human, and unapologetically personal. This is my corner of the Internet, and I’m going to make it mine. If it doesn’t fit into someone else’s idea of what a blog should be, good. I’d rather be weird and interesting than boring and polished.

Photo of an old bleach.org website design, circa 2001
Remember splash pages? They added a click to get to the content but set the stage for the experience and had so much personality.
Another photo of an old bleach.org website design, circa 2001
I guess we can’t blame mobile keyboards for kids not using proper capitalization in their writing…

So here’s to 2025. Here’s to ditching the algorithm and shouting into the void on your own terms. Post on your blog, not on Twitter or Instagram. Make something wild and put it online, even if it’s just for you. Break the rules. Take a risk. Channel your inner AngelFire. Redesign it when you’re bored. Let’s bring back that early Web energy—the one where you didn’t need permission to create, and the only limit was your imagination.

If you’ve been thinking about starting a blog, do it. The Web needs you. It needs your weird. And who knows? Maybe 20 years from now someone will stumble across your site and fall in love with the Internet all over again.

Three Gadgets That Transformed My Home Office in 2024

Working from home as a software product manager means spending a lot of time at my desk, whether it’s in meetings, collaborating on projects, or diving deep into strategy. This year I added three gadgets to my desk that have genuinely improved my life and comfort working from home.

Quntis ScreenLinear Glow RGB Pro+ Monitor Light

Winter evenings in Montreal get dark fast, and by mid-afternoon, my office used to feel a little dreary. Enter the Quntis ScreenLinear Glow RGB Pro+, a monitor light bar that’s now an irreplaceable part of my setup. Here’s why I love it:

  • It illuminates my desk and keyboard without casting glare on my monitor;
  • The wireless remote makes adjusting the brightness or color temperature a breeze; and
  • The RGB backlighting is a cool alternative to LED light strips, casting a colourful glow to the wall behind my desk to create a relaxing ambiance for those late-afternoon (and late night) work sessions.

I had never used a monitor light bar before; this is proving to be a great alternative to a traditional desk lamp and seems effective in reducing eyestrain long hours in front of the screen.

Elgato Stream Deck+

I never would have thought that a gadget designed for streamers would become indispensable for managing my day-to-day work, but the Elgato Stream Deck+ has been a game changer. While its customization possibilities are endless, I’ve set mine up primarily for controlling Microsoft Teams. I love being able to have one-tap access to physical buttons that:

  • Turn my mic and/or camera on or off;
  • Send reactions like a thumbs-up or clap during meetings; and
  • Hang up calls when a meeting wraps up.

I’ve got a few other things setup on here including:

  • Using the knobs for volume and media controls; and
  • Some Figma shortcuts to align things on another page.

That’s all I really use it for, honestly. At first blush, $300 is a step price for basic controls like this, but I find it much more satisfying to use and faster than fumbling with mouse clicks or keyboard combinations.

Kensington Slimblade Pro Trackball

Switching to a trackball this year felt like a bold move. Let me tell you: 18-year-old me would absolutely laugh at this decision. I mean, isn’t a trackball what tech nerds from the ’80s used?

Well, older (and hopefully wiser) me now realizes how amazing this thing is for ergonomics. A few years ago, I upgraded from a traditional mouse to a Logitech MX Vertical, which was a huge improvement for wrist strain. But the Kensington Slimblade Pro takes it to another level. Here’s my setup:

  • Bottom left button: Left-click
  • Bottom right button: Right-click
  • Top left button: Close windows (Command-W on macOS)
  • Top right button: “Back” in apps/browsers
  • Combo – top right + bottom right: Move “Forward” in apps/browsers
  • Combo – bottom right + bottom left: macOS Mission Control

The precision and comfort of the Slimblade have turned me into a trackball convert. I don’t miss moving a mouse around at all, and the improved ergonomics make long workdays much easier on my wrist. I also picked up a their ErgoSoft Wrist Rest which I find compliments the trackball well. Also, I don’t find it too bulky to throw into my bag to bring with me for days in the office (which I can’t say about my Logitech ERGO K860 keyboard, but I still lug it with me anyway).

I think I’m officially a trackball user for life.

These three gadgets have genuinely improved my happiness and comfort (which ultimately makes me more productive, right?). If you’re thinking about upgrading your home office setup, I’d highly recommend giving one (or all) of these a try! You might just find, like I did, that small (and relatively low cost) changes can make a big difference.

Books That Have Influenced My Career and Shaped Who I Am Today

Following a recent conversation with a mentor I compiled a list of books that most profoundly influenced my career and leadership style. It’s interesting to look at this list holistically because there is a mix of business, technical, and “general life” books that have shaped who I am today.

  • Radical Candor
    Worth it’s weight in gold, this book taught me about caring personally with every business interaction. I realize now that I used to think I was just being “direct”, but in work relationships I was in fact , and sometimes disrespectful. This book taught me how to be direct while caring personally, which has greatly improved my working relationships (and the business outcomes!)
  • Speaking as a Leader
    Another mentor once suggested this book to me, and although it’s not as easy to read as some of the other books on this list, it did teach me to watch my words and to have intent with everything I say in meetings, on calls, etc. As a product manager what I say is often taken as gospel by R&D, marketing, sales, etc. so this was an important learning for me (whereas previously I would sometimes ‘vent’ in public forums, etc.)
  • The Power of Habit
    I do not strive in chaos; my leadership, and product management style, is to “set and forget” as much as I can. This is also how I manage my money, investment, etc. At work, this means defining a governance framework with agreed upon templates (project reporting), cadence (weekly meetings), and discipline (e.g. get out of email and add topics to the weekly meeting agenda for a proper discussion and review). These are examples of team habits that I’ve built into managing my teams and areas of business which I learned from this book! (Make a habit of it!)
  • Managing Humans
    I originally read this when I crossed over from being a web developer to managing web developers but the advice presented here can apply to any leadership role. I’m a big fan of the author’s leadership style, his blog and his podcast.
  • Don’t Make Me Think
    This is an old one from my web developer days and it’s mostly about web site usability. But, I would argue that the title alone is a great learning for anyone building products or a company that markets products to… anyone. I still refer to the idea of “don’t make the think” and insist on keeping all of my work as simple as possible.

Honorable mentions:

  • Grit
    Grit was a leadership principle I was introduced to during my time at TELUS, and the basis for their management training curriculum that I was lucky to have completed during my time at the company.
  • Start With Why
    I sometimes ask myself how practical Simon Sinek’s advise can be in real world companies at enterprise scale, but I think there are many good ideas in his teachings. The advice here, I find, can apply to both my work (why are we doing something, etc.) and my career (why am I doing what I’m doing, am I going where I want to go, etc.)
  • Man’s Search for Meaning
    A short but powerful read about one man’s memoir and survival of Auschwitz and other camps. This book has equally shaped my personal and work life, and I re-read it every five years when I feel I’m taking things for granted or just having a tough time in my (frankly) cushy and privileged life (and job/career for that matter).

Shifting from Digital Project Delivery to Product Development

I originally published this thought on April 8, 2019 to the Rogers Digital blog. I’ve since moved on, but I thought this was worthy for republishing here to kick-off thoughts about my work. Enjoy.

It’s an exciting time to work at Rogers Digital. As Lisa mention in her inaugural blog post, we’ve been quietly building a new digital team that’s passionate about solving our customers’ biggest issues.

A key function that we’ve introduced to Digital is Product Management, including a new role: Product Owner (or PO, for short).

This has forced us to stop talking about what’s in- or out-of-scope to deliver a project, and be careful that we don’t simply avoid doing something by labelling it “scope creep” as something that “isn’t part of our Minimum Viable Product”. In a project world, anything that isn’t delivered as part of the project may never be delivered (and often never is), and this has led many business leaders to take a “fit it in while you can!” approach to additional scope. Instead, we’ve defined products for which we rigorously prioritize, and regularly debate the order of, an ever-growing list of enhancements to improve our customer’ experience.

Here are just a few of the things we’ve learned must be considered when introducing Product Management to a traditionally project-drive culture:

  • First, define your products and product components – An ill-defined product portfolio sets anyone with a “Product Owner” title up for failure out of the gate. POs will grow resentful of leadership if their area of focus keeps changing and they don’t understand (and agree with) associated KPIs.
  • Fund your products – A well-defined product portfolio will allow some flexibility in how you allocate capital as well as provide checks and balances. It is important that you empower your Product Owners and give them the resources they need to the deliver the results (targets) you’ve agreed to. Without funding for PO initiatives, either to work with an in-house product development team or with external partners dedicated to their product, there will be a lack of accountability, not to mention the sense of accomplishment and pride, for your POs.
  • Assign one Product Owner per product (or product component) – Depending on the size and complexity of your products you may need different Product Owners to oversee different components. No matter how you slice it, the PO should be the single point of contact for your development and operational teams. If you have multiple POs working on a single product, designate a Chief Product Owner (CPO) as the decision maker and ensure that other teams understand this responsibility.
  • Let your Product Owners take risks and fail quickly – Big, cross-functional projects can fail horribly with a single missed requirement, but products generally don’t. POs are masters at finding the balance between what your customers want and what your customers need, and the best products (and Product teams) thrive by taking calculated risks, making mistakes early, and learning from them, in order to continuously improve their products.
  • Establish the right governance forums – Try to stay out of your POs hair day today and let them do their job! Executives often like to drop “checkpoint” or “alignment” meetings into people’s calendars to “deep dive” into… something. It’s best to avoid ad hoc meetings because they often lack structure and cause anxiety within your team. Instead, define governance forums that work for you and your executive team so that managers and executives are kept abreast of your progress in a way that is structured and lets POs keep their momentum.
  • Re-define Project Management and ensure roles and responsibilities are understood by all teams – Depending on your development methodologies (e.g. Scrum, Waterfall, etc.) you’ll need to re-define how Project Managers work with each of your teams. Unless you’re a start-up, it’s likely that your Digital team has employed Project Managers for many years, and once you introduce Product Manager, Scrum Masters, and other newfangled titles into the mix, roles and responsibilities quickly get diluted. Come together, build a RACI together (it can be fun, really!), and educate teams on new and evolved roles and responsibilities in order to get everyone on the same page.
  • Finally, clearly define the Product Management career path within your organization – I can’t reiterate this enough, but who wants to take a dead-end job? Often times, especially in larger organizations, POs are told they’ll be the “CEO of your product”. Sounds impressive, but if you’re the CEO, where do you go next? POs need to understand how they can grow within the Product organization, and clearly defining a path from PO to increasingly senior roles, such as Chief Product Owner, Group Product Manager, and Director of Product Management, give your POs something to work towards within your company. The last thing you want is for your superstar POs to leave for bigger roles at your competitors!

The role of Product Management and responsibilities of Product Owners and Product Managers differs from company to company (and often from one business unit to the next within the same company). From the perspective of a Digital team within a large telecommunications company, it can be challenging to define product ownership because of the complexity of our business and overlapping, complex technical systems.

We’ve made great progress as a team and we’re ramping up our velocity in 2019! We’re always on the lookout for good Product Owners and Product Managers, so if you’re interested in joining the team it would be great to see you at our next Open House!

Read more thoughts…