ownpath

Had a really interesting conversation with The Ken recently around a question that’s becoming increasingly important for design. If AI automates away the grunt work that junior designers traditionally learned through, how do they develop judgment and become senior designers? My view is that most critical professions that trust young people with responsibility have rigorous simulation environments built into the system. A 22-year-old can lead a contingent in the army. Fly planes. Assist in surgeries. Not because they magically became capable overnight, but because they trained in environments that simulate consequences before the real thing. Design largely doesn’t have that. A lot of design education is still hypothetical projects, portfolio exercises, and conceptual prompts disconnected from real users, constraints, tradeoffs, and feedback loops. So now that AI is removing a lot of the repetitive work people learned through, the gaps in the system are becoming more visible. Which means designers increasingly have to create their own informal structures of apprenticeship and simulation. Building side projects. Shipping things. Finding mentors. Getting feedback from real people. Learning in public. Creating their own reps. The hopeful part is that, in my experience, young designers are actually incredibly enterprising. They learn fast, adapt quickly, network hard, and are far more resourceful than people give them credit for. I’m pretty confident they’ll figure it out. PS: Was lovely jamming with Praveen Gopal Krishnan and Jay Dutta on the pod. Curious for you to check it out and share your perspective! PPS: We’re hiring product and brand designers at ownpath. Feel feel free to apply on our site or DM :)

Our founder, Shreyas Satish, spoke to Praveen Gopal Krishnan and Jay Dutta on The Ken podcast about one of our favourite topics — design apprenticeships. And rumour has it, there's spirited debate and hot takes. 👀 We're tuning in tonight, dropping notes tomorrow! 🍿

A design system is only good if a stranger can pick it up on a Monday morning. Last year, Anish, our Design Lead, was working with the team building the website for VIDA, Hero MotoCorp's EV mobility brand, ahead of the VX2 e-scooter launch. Fast timeline, multiple teams contributing and a lot of moving parts. One of the things he focused on wasn't the screens. It was the system underneath them. How components were named. How tokens were structured. How the whole thing was laid out so that anyone who came after; a different designer, a developer, or someone from VIDA's internal team, could open it and immediately know where they were. That's harder than it sounds. Most systems are organised for the person building them. Anish built it for the person who'd inherit it. Here's what that actually means in practice: - Build for the editor, not the author. The person maintaining this in six months may not be you. Design for them. Build it so the next person who picks it up is ready to go. And even if it is you, build so that you don’t lose context while working on multiple projects. - Document the decisions, not just the outcomes. A component without context is a trap. The why matters as much as the what, especially when the person reading it wasn't in the room when the call was made. - The closer your design files are to the final product, the less gets lost in translation. Spec it like the developer is you, because the gap between what you meant and what ships is almost always a communication problem, not a capability one. The goal isn't a perfect system on day one. It's a system that's honest about what it is, easy to contribute to, and harder to ignore than to use. We're unpacking the full VIDA World project soon. More on that shortly. PS: We're hiring a Senior Product Designer. If this is how you think about your work, you'd fit right in here. We work with Hero MotoCorp, Philips, and a handful of ambitious startups building products people actually use. Apply through the link below.

One of the most common questions designers ask early in their careers is how to inculcate better taste so their visual design skills can improve. In a session from the ownpath archives, Vinu Remesan (ex-Creative Director, Gojek) explained that improving visual design doesn’t begin with tools or inspiration, but with learning how to look at products differently. Many designers search for inspiration in galleries like Dribbble or Behance. But the most valuable design references are often much closer: the products that are at our fingertips every day. Read the full piece on the ownpath Substack, linked in the comments below.

Static screens have always struggled to represent dynamic product behaviour. Hover states, dropdowns, conditional logic, transitions, and multi-step flows are central to how products actually function, yet they are time-consuming to simulate convincingly. As a result, teams often prototype less than they should, relying on imagination to bridge the gap between screens. With AI-assisted tools, we’ve been able to move from a rough idea to a working, interactive prototype in hours rather than days. These are not polished systems or pixel-perfect interfaces. They are behavioural models—artefacts that respond, transition, and flow in ways that approximate the real product. So now, instead of investing heavily in polish before direction is validated, teams can externalise ideas quickly and interact with them before they harden. Read the full article on the ownpath Substack, linked in the comments.

Most product teams have access to troves of data. Metrics are tracked, experiments are run, dashboards are shared in weekly reviews. And yet, despite the volume of information, clarity can remain elusive. What’s often missing is not more data, but a structured way to interpret it. In his session from the ownpath archives, Vineet Nandkishore (ex-Senior Consultant, Fractal) proposed a more structured way to think about designing with data. Not as dashboards or A/B tests alone, but as a system of levers that shape every product decision. He introduced us to IESS (Intelligence and Emotion at Speed and Scale), a framework his team at Fractal used in AI consulting engagements with Fortune 100 companies. “You might not necessarily have the answers to these questions, but it is important for you to understand these levers so that you can ask the right questions,” he explains. Read the full article on the ownpath Substack, linked in the comments below.

Brand strategy has become increasingly visible and structured over the last decade. There are frameworks now. Playbooks. Notion templates. Miro boards. Structured workshops with tidy outputs: purpose, vision, values, tone, archetype. But in her session from the ownpath archives, Kritika Trehan (Founder, Studio Ping Pong) offered a nuanced take on the need to balance a systemised approach with the sensitivity that each project demands. Compared to graphic design or advertising, brand strategy as a formalized practice is relatively young. As markets have become more saturated, the demand for differentiation has increased. And with it, the need for clearer strategic thinking. That has led to systemization. Agencies have built processes. Studios have defined stages. Deliverables have become standardized. And yet, the work itself refuses to become mechanical. No two founders walk into a room with the same clarity. No two businesses are at the same stage of self-awareness. Some need structure. Some need reassurance. Some need confrontation. Kritika recommends an approach that adapts to the needs of the client you’re sitting across from. Read the full article on the ownpath Substack, linked in the comments below.

Cutting-edge startups building what’s next. An industry-leading automotive brand. Different stages, different scales. But the same standard of craft. Here’s a glimpse of the brand work we’ve been creating for our clients at ownpath Studios. We're now hiring Brand & Graphic Designers to work on more such projects. If you want to create work that’s thoughtful, precise, and built for impact, we’d love to hear from you. We’re looking for someone who can: • Shape and refine brand identity systems • Design marketing and campaign assets across touchpoints • Translate ideas into clear, cohesive visual execution • Maintain craft and consistency across every touchpoint Competitive pay. Flexible setup. Mentorship from senior designers to ensure you're always honing your craft. Apply at the link in the comments.

For a long time, documentation and research sat slightly outside the core of product work. Important, yes, but often slow, manual, and disconnected from the pace at which teams were expected to move. Research lived in decks. Insights were buried in long documents. Context was lost between interviews, summaries, and handoffs. AI hasn’t changed why we do research or documentation. But it has changed where the work lives and how close it stays to the product being built. There is now a high degree of confidence in the information stored in research documents. As a result, we’re able to go back to source material, ask better questions of the data, and ground decisions in what was actually said, not what was remembered. Research stops being something you “wrap up” and becomes something you can continuously return to. Read the full article on the ownpath Substack, linked in the comments below.

Product teams building with AI often focus on capability—model improvements, latency reductions, performance benchmarks, and such. But users don’t experience any of that directly. What they do experience are things like suggestions, predictions, and recommendations. And then they decide whether to trust them. In his session from the ownpath archives, Akshay Kore (Author, Designing Human-Centric AI Experiences; ex-Head of Product Design, Suki) shifted the conversation away from model performance and toward a soft skill: how AI systems engender trust from users. His session can be compressed into this one simple thesis: Trust in AI is not a binary state; it is calibrated gradually through interface decisions and brand perception. For design and product leaders, that calibration is now a core responsibility. Read the full article on the ownpath Substack, linked in the comments.