Hello!
Today I'm thinking about job hunting, specifically that the world you're applying for a job in no longer exists. There are remnants of it in bigger, older companies, but not for long. Why? Because the job descriptions most people are applying against assume a workflow that's already gone. For years, designers worked "out ahead" of engineering in mockups. Now development teams are "out ahead" of design, with new features becoming code at a furious pace, and design's job shifts toward making all that output fit together. At the Design Futures Assembly this spring, close to half of designers had shipped AI-generated code to production, and at the best teams the "stack" was dozens of internal tools that change month to month. Try writing a stable job req for that. So the natural reaction is to grab every tool and try to do every role. Designers pick up coding agents, developers spin up layouts, and everyone ends up here: That approach spreads us thinly across multiple complex and important jobs. I can play a developer on TV, but in real life I'm a pretty crappy one. The better move is the lesson we taught designers at Yahoo! years ago: double down on the thing you're uniquely good at and apply it elsewhere. So if you're looking for work right now, don't optimize for the job posting. Get hands-on with the tools, figure out what they can and can't do, and show how your particular superpower reaches further because of them. That's the job that actually exists.
What specific indicators should I look for in a portfolio to demonstrate my ability to solve problems rather than just showcasing team processes?
Here's the simple test I use when I'm sitting through a portfolio review: if I removed every slide about meetings, sign-offs, and stakeholders, how much would be left? In an hour-long presentation, most of the time often goes to organizational challenges and processes, with little left for design skills. And that's a reflection of your ability to operate within an organization, not your product design sense.
So what should be there instead? A few specific indicators.
First, a clearly framed problem. One of the most valuable things designers learn is not to jump to solutions, or start from a solution and then figure out what problem it solves. Defining the problem is creative work too. A well-defined and exciting problem (and its constraints) is the catalyst that makes design go. If your case study opens with "we were asked to redesign the dashboard," you've skipped the most interesting part.
Second, the problem made visible. Designers have the ability to actually show the problem. At eBay, Jamie Hoover's registration diagram showed drop-off rates behind every step of the flow, so you could actually see users dropping off, which meant money being lost. That kind of artifact tells me far more about how you think than a project timeline.
Third, alternatives and iterations. Good design involves the simultaneous creation and evaluation of multiple alternatives. Show me the paths you explored, the ones you killed, and why. What iterations did you go through to get to the final solution?
Fourth, the why and the how, connected. Walk through the "why" at a big picture level, and then the "how" at a detailed level. The strongest presentations connect the pixel-level process to an understanding of business, product, and user goals. Why is this button here? Why this layout over the other three you tried? (And "the design system had a component for it" doesn't count as an answer.)
Fifth, your contribution, specifically. Focus on the concrete things you personally accomplished and the way you accomplished them. The question I'm always trying to answer is how your unique contributions as a designer, not just as an employee or team member, made the impact you intended. Lots of "we" with very little "I" is a red flag.
Practically, this means fewer projects and more depth. Go deep on a couple of examples, keep the bio short (we've all read your resume), and spend your time on the decisions only you can explain.