Kirk Gustafson

Portfolio tip for design leaders: Unless your values/leadership style/‘how I lead’ slides are unique or clearly showing why they make you a good fit for this specific role, skip all that in your portfolio presentation. It’s a waste of time and if it sounds like what all the other candidates are also doing(which is true 90% of the time), it will make you blend in. Not good: Generic words like empathy, team building, servant leadership etc Good: Super specific values that apply to this role Better: Super specific values that are actually then evidenced in the work you will shortly present

94

11 Comments

If we're not talking about design maturity, agile process, or craft, then us designers are probably talking about ✨quality.✨ I certainly see my interviewer's eyes light up when I mention this magical word. "Design is the one that has to hold the quality bar," I tell them. But what if that didn't have to be true? For a truly high-quality product, I don't think it should be design holding the line. It has to be something baked into the organization - everyone holds the quality bar. Even though "quality" is a slippery thing to define, if we can define it and hold ourselves to it, we can reduce the tension in the org and start to think less about the mere baseline quality for the product and more about raising that bar - delighting the user. I very much enjoyed Luke Anthony Firth's take on how they folded quality into their product building process. Have a read! https://lnkd.in/g4SenmYZ #designleadership #productprocess #productdesign #productquality #designquality #opentowork

4

Research is a function of strategy.  "According to CB Insights, over 90% of all products fail, most commonly due to no market need." Leave yourself time to ask big questions about whether any actually needs your product or service before you decide to launch it. #UXstrategy #UXresearch #Marketresearch

3

1 Comment

It has been my continuous struggle to showcase the contributions of the design team to business. Slapping the rules at product level seems unjust. Finiding out a comparative for a specific feature becomes difficult to assess. I am on my journey towards putting a right measuring metrics for the same. Let's connect if you are also looking out or something that might have worked well for you. #uxdaily #productmetrices #designmetrices #productstrategy #designstrategy

8

2 Comments

My top 3 project selection tips for design leaders doing portfolio presentations: 1. Pick projects that have a good mix of what you did directly plus what the team did. Very rarely is anyone looking for a pure people manager while hiring a design leader. Your personal contributions need to stand out in your work. It doesn’t have to be IC work (but if you do that, show it). It could be a doc you wrote, an insight you uncovered, a strategy you formulated etc. Differentiate between what you did yourself, what you directed the team to do, and things the team might have driven independently. Make this distinction clear as you present your portfolio. People want to see you can do smart stuff yourself, can direct a team well, but will also build a high functioning team that does good work. Also, if you would like I can do a separate post in these 3 modes of operation for any design leader. 2. Pick projects based on the role you’re applying for. It doesn’t have to be and most certainly won’t be a 100% match. But for example, if what the team needs is scaling a successful product, pick examples where you enabled scale. This needs to be deeper than “I’m applying for fintech so here’s another fintech project”. Your project selection should show you understand the challenges for the company and have transferrable skills. 3. Pick projects where you can show both macro and micro user insights. Scale the macro according to your seniority and level. For example, if you’re applying for a Director role, you better have projects that show you driving user insights at Director scale (for instance something that drove resourcing decisions). At the same time, the project should also show micro insights appropriate to role. For example, key interaction design flows redone by your team for the goal. Or even things like font/color selection and how that drove impact. Use these guidelines and apply the filter for what fits with your past experience and this new role. If you have the same portfolio presentation for completely different roles, something is off somewhere. You only need to present 2-3 projects in a presentation, pick the most appropriate ones. If this sounds complicated and like a lot of work, it is. Project selection is THE foundation for how your presentation will play out.

208

13 Comments

"The strategic design gold rush is over." While this might sound like a scary sentiment at first, I'm choosing to see it as an opportunity for design leadership. It's a chance for reinvention of what role design led teams can play in corporate settings. Users are increasing their demand for simple and straightforward user experiences. Every company continues to need more user and customer advocacy and design leaders are perfectly positioned to be the fabric of that advocacy and stitch together the functions required to deliver it to market. Rather than being relegated to a subordinate capability in product-led companies, design leaders can now redefine their purpose, leveraging their skills in user empathy, strategic experiential planning and continue to tie together the often disparate agendas at play in organizations. #Design #Leadership #Reinvention #Innovation

3

1 Comment

Most designers are trained to present work to our peers, but as your career matures, your audience expands to include many other departments who don’t speak “design”. This article resonated with me and offers some sage advice about the use of storytelling and a “business lens” to craft more compelling presentations. #ProductDesign #Storytelling #UserResearch #BusinessObjectives

9

Ever wondered about the power design has to align teams? I just published a note I've shared with cross-functional teams in the past that highlights the importance of getting to a concrete discussion quickly, and the role design can play. Concrete Elephants: How to turn the lights on for your team

49

5 Comments

I'm thrilled to share that my latest product and design discovery article is live on Mind the Product! As a consultant, I've observed that the term 'Discovery' can have varying interpretations across different teams. It's not uncommon to encounter a team deeply immersed in a solution yet lacking a shared understanding of the customer opportunity they're addressing. At Lab Zero, we meet clients where they are and advocate for discovery while maintaining flexibility. We often employ lightweight methodologies to foster a shared understanding, even when work is already underway. Teresa Torres' book “Continuous Discovery Habits” is a guide to developing the mindset and practices that enable teams to discover and deliver value to their customers throughout the product development process. Her explanation of the 'Opportunity Solution Tree' helped me articulate a process for asking questions and bridging gaps when joining a new team. The first part of this two-part series looks at reversing the 'Opportunity Solution Tree' to establish a connection between the ongoing solution, customer opportunities, and business outcomes. The second part (coming soon!) will explore strategies for identifying gaps in your team's understanding of customer needs and the necessary measures to mitigate risks before launch. This series will help consultants, new team members, or a struggling team connect with that all-important why and launch valuable experiences for their customers and their orgs. Have you tried something like this with your team? Feedback is appreciated! If you haven't explored Mind The Product's extensive content library, I highly recommend it! In addition to articles about discovery and understanding customer needs, the community has shared insightful perspectives on product leadership, business, and teams. It's a great place to see perspectives on processes and theories informed by real-world use.  #ProductDiscovery #Design #Discovery #ContinuousDiscovery #Onboarding #Risk #CustomerOpportunity #Value #BusinessOutcomes

13

6 Comments

Diversity in design isn't just a buzzword—it's a business imperative. 🌈 As a hiring manager, I've seen firsthand how diverse teams boost creativity, product quality, and profitability. I believe in building teams that reflect our users and bring fresh perspectives to every project. How do you ensure fairness during the hiring process when you have to look at portfolios? Here is my perspective on the challenges of inclusive hiring. #DiversityInDesign #InclusiveHiring #TeamBuilding

29

3 Comments

Are you ready for the rise of fractional design leadership? Here's my prediction: 👉 By the end of 2024, companies will commonly engage design leaders in a fractional capacity. 👉 This could either look like... A. Design leaders engaging in contract roles to strategize and lead specific product initiatives supported by in-house teams. or B. Design leaders joining agencies specializing in fractional leadership, creating a leadership-as-a-service model. This could include additional support from teams sourced from either the agency or the client. 👉 Companies right now are balancing cash flow with growth and innovation. The increasing risk of disruption in every industry underscores the need to adapt to survive. Fractional leadership can jump-start areas where product teams feel 'stuck.' Moreover, fractional opportunities can unlock significant career-growth opportunities for designers, a path that is traditionally more scarce and has lower turnover than IC roles. What's your take on this? Is fractional design leadership the future, or am I completely off? 🤔 #management #technology #careers #leanstartups #future

2

1 Comment

We have a large project that's primarily handled by my Design Director and PM—it's straightforward, but has a very detailed process associated with it. Review, QA, documentation all needs to be handled very specifically. So when we had an upcoming client review and we knew these team members would be out on PTO—we got together ahead of time, documented the process and debriefed two brand new team members who would fill in. And oh boy did it go...great. Document or Die folks. #yesterlearnings #prepare #documentation

3

As Senior Designers, we have to assert our importance in business decisions to show that we are just as crucial to their organizations as any other senior role. It first starts on a personal level. We have to realize we're not just here to make great design; we're not just here to be the voice of the user; we're here to provide intentionality in every aspect of organizational thinking. "And, while the compensation looked quite good relative to what designers were earning even in senior roles at established design firms, it did not necessarily match senior finance, sales, or engineering jobs." This quote from the Article is what really hits home with me. https://lnkd.in/epemebmx

3

I'd like to share some valuable lessons that have completely transformed the way I approach communications. Plus, I've added some tips for product designers and design partners. 💡Case 1: Answer the Question I thought I knew how to answer questions until I got this feedback: "When an executive asks you a question, start with a clear 'yes' or 'no', or state 'I don't know, but I will get back to you by X date'." While variations exist, the key is to answer the question first. Too much information usually doesn't help - Answer the question, then let them ask probing questions. This advice resonated with me so much that I created a desktop wallpaper to look at it every day. 🤝 Case 2: Manage Meeting Effectively Another tip I learned is how to manage meetings. Based on tips from mentors and coworkers, here are three essential points to remember: 1. Why we are here: Ensure every meeting has a clear purpose. No one has time for irrelevant meetings. 2. What we aim to achieve: Clearly define the meeting's objectives. 3. What decisions we will make: Identify decision-makers and criteria.
 Applying this to design meetings, merely sharing in-progress designs often lacks value. Instead, structure the meeting to: 1. Clearly define the meeting's purpose and type: For example, specify if it’s a review and instruct people on the type of review you need. 2. Clarify the objectives: Are we finalizing designs to send to engineering, or aligning on problem statements with products? 3. Identify decision-makers and criteria for decisions: Then, make a decision. Of course, in both cases, summarize the outcome of the meetings and share it right away. ✨ Case 3: Clarify Expectations At workplaces, confusion and fires happen. Sometimes you're not sure what's going on. You don't want to overpromise or overstep, but you need to know what action is required. When I heard this question "What am I accountable for?" in the middle of a foggy meeting, my brain just cleared. Yes. We need clear ownership and accountability to navigate ambiguous situations. It was a sentence that resonated with me, and I still remember how we were able to move on to the next steps. To build on this, I also advise my partners to communicate their asks clearly. I hear a variety of design requests. Some people articulate their asks with intended outcomes, expectations, and timelines, while others just share desires and disappear. Clarity in your asks is key—it's almost a job requirement. Remember, others can't read your mind. If you believe in your idea, it's important to articulate it clearly. #CommunicationTips #ProductDesign #DesignPartnerships

35

6 Comments

Really annoyed at Figma's price gouging here. There is no reason other than greed: https://lnkd.in/gfdrEiWH Oh, and I emailed them about it and this line from their reply was particularly poignant: "Additionally the minimum for enterprise is a $5k invoice minimum. 6 enterprise seats or made up with other products." To put that in context... our monthly Adobe bill (for 8 CC, 7 PS, 6 Acrobat licenses) is ~NZ$2k... Amazing how quickly enshittification sets in... #Figma #Design #SoftwareLicensing

8

3 Comments

What Is Neurodesign? Designers can create more effective and engaging products by working synergistically with users’ brains. #UX #productDesign #Neurodesign https://buff.ly/3Wf9xXe

3

I’m developing a theory about why so many people find it challenging to learn how to use a piece of software. I would love it if y’all can help me refine this idea. It’s inspired by years spent as my entire extended family’s tech support and teaching students in UX learn tools like Figma on their own. My theory is that people tend to assume if they don’t know how to do a thing in the software, then there are one of two problems. 1. The software doesn’t do it.  2. It’s incredibly complicated and not worth bothering with. These limiting beliefs inhibit their sense of agency and hamper their ability to search for something. The result is people who either don’t bother searching for a solution, or who give up too easily after attempting a search and defaulting to belief 1. However, more recently I’ve started seeing another missing piece of this puzzle. People seem to have forgotten why computers were invented in the first place. They are at their core productivity machines. Long before entertainment came to our computers, they were for engineers and secretaries. Their primary utility was saving time doing mundane tasks. But if you don’t internalize that, you perceive computers as these mystical boxes of tech that are hard to understand. As a result, your primary assumption about any block with a piece of software is that it must be you who are “stupid” or “incapable” of making it work. Similarly, you may believe that if this is cumbersome for a person to do, it must be cumbersome for a computer as well. But if we can get students to flip this mental model and always remember that machines were, first and foremost, meant to alleviate tedium in basic tasks, then we empower everyone to search for a solution. And when no solution can be found, they should be mad at the machine for being insufficient, not wrongfully assume it’s their own incompetence. As a teacher, I haven’t figured out if this is objectively true, but my observations have led me here. Now, I am trying to figure out how to make this a teachable skill. 

10

11 Comments

Book Recommendation: Product people, especially Product / UX Designers, can greatly benefit from reading (or listening to) The Power of Moments. It's a goldmine of insights. My key takeaways include: 🔹 Impactful moments often thought to be kismet or by chance can be intentionally created for others. 🔹 Develop a plan to address significant life events your customers may encounter before they occur (e.g., birth, death, graduation). 🔹 Embrace intentionality in your approach to create powerful moments for your customers, and team members. The frame of mind this book creates is incredible. I think about it on a monthly basis. Enjoy! #ProductManagement #UXDesign #ProductDesign #UserExperience #BookRecommendation #Intentionality #Leadership

4

Is it just me World Usability Congress or should your website adhere to at least WCAG 1.0 standards? Text as an image over video, days with no month or dates, white text on teal, no ability to tab through content, hover drop-down menus... woud be great to see this brought up to a level its intended to represent. https://lnkd.in/gwU5mGim #usabilitystandards #accessibility #customerexperience #designstandards #ux #cx #uxaudit

14

4 Comments