Working in digital design isn't what you see on social media
The reality is a lot more tedious than people expect. You spend most of your time wrestling with file formats, dealing with clients who can't articulate what they want, and learning tools that become obsolete before you've actually mastered them. When I first started out, I figured skill alone would carry me. It doesn't. The people who actually make it are the ones who understand the business side — contracts, pricing, positioning — and who can pivot when the industry shifts under their feet. I came across Jessica Ann Collins a while back and found her trajectory actually useful to study, because it mirrors something I've seen repeatedly in this field. She started as a visual graphic designer — the kind of role where you're taking direction, executing comps, and usually earning less than the work is worth. That's not a criticism of her. It's just the entry point. Most people I know began exactly there. What she did next is what separates the people who stay stuck from the ones who move forward. She shifted from purely visual output into digital innovation. That means she stopped being someone who only makes things look good and started solving problems with digital systems. She moved into areas like interactive design, product strategy, and likely some form of emerging technology integration. The exact details of her portfolio aren't what matter here — the pattern does.
Here's what I learned watching that kind of transition play out in real projects I've been involved with: the shift from graphic design to digital innovation requires you to become comfortable with code-adjacent thinking without necessarily becoming a developer. You need to understand how interfaces behave, how data moves, and how user flows break. I worked on a project once where the designer had zero background in design systems and spent three weeks relearning grid structures, spacing scales, and component states because the client's design tool had updated and nothing aligned anymore. The workaround was building a single reference document with exact measurements and sharing it across the team. Saved the project. The counter-intuitive part that beginners miss is that technical skill matters less than communication in that transition. You can learn Figma in two weeks. Learning to translate between stakeholders, developers, and executives takes years. Jessica's career seems to reflect that — the move from "making visuals" to "driving digital products" is fundamentally a communication and systems-thinking shift, not a software upgrade. One thing worth noting honestly: this path has real bottlenecks. Not everyone has access to the kind of mentorship or project variety needed to make the jump from execution to strategy. Junior designers at smaller agencies often get stuck on production work for years because there's no one handing them more complex responsibilities. If that's your situation, the workaround is self-directed — take on open-source projects, rebuild interfaces from apps you use daily, and document the process publicly. It's not glamorous but it works.
Another limitation people don't talk about: the title "digital innovator" is vague and means different things at different companies. At a startup it might mean you prototype everything. At an enterprise it means you sit on committees. Don't assume the title itself represents skill. Look at what problems someone actually solved and whether you could replicate that work yourself. There's also the question of tools. The landscape changes constantly. When I was moving from print to digital around ten years ago, we had maybe four relevant platforms. Now there's dozens. The key insight here is that tool familiarity is temporary. The underlying principles — visual hierarchy, information architecture, user psychology — don't change. Spend less time chasing every new feature release and more time understanding why certain layouts work regardless of the software you're using. From a practical standpoint, if someone wants to follow a similar path, start by picking one area of digital product work and going deeper than your job requires. Learn the basics of prototyping in Figma or Framer. Understand how a basic API works. Read about accessibility standards and apply them to your own designs. Then expand outward. It's slower than people want but it builds something durable instead of a shallow portfolio full of trendy-looking mockups.
Get the Full Details
The thing about Jessica Ann Collins' career that stands out to me isn't any single achievement. It's the pattern of moving from execution into creation — from someone who was given a brief to someone who decides what the brief should be. That's the real shift. Everything else is just tools and titles.
