Great products don’t start with wireframes. They start with clarity about users, alignment among decision-makers, and a roadmap that minimizes risk instead of creating it. To explore how that plays out in real projects, our Co-Founder, Karol Kaczmarek, spoke with Makoto Kern, a UX product strategy leader at IIIMPACT, who has helped enterprise and B2C teams deliver software for energy, logistics, robotics, cybersecurity, and other complex sectors. His message is clear: user-centric thinking outperforms feature-centric speed. In industries driving sustainability and energy transition, that mindset turns abstract ideas into tools that truly work and endure.

🎙️ Watch our full conversation with Makoto Kern, UX Product Strategy Leader at IIIMPACT, where he explains how user-centered product strategy helps climate tech and energy innovators reduce risk, speed up delivery, and build software that teams actually use. He breaks down why early alignment matters, how enterprise UX differs from consumer UX, and what companies can do to turn complex ideas into practical digital tools that support the energy transition.

What Makes a Strong Product Strategy

A solid strategy begins with understanding the problem before designing a solution. Too many teams rush into visuals and layouts, only to face costly redesigns later. Kern emphasizes the importance of alignment between leadership, design, and development from the very start. He jokingly calls this initial step a “therapy session,” where everyone sits together to define goals, KPIs, and trade-offs. When this alignment is achieved early, it prevents miscommunication, avoids redundant work, and grounds every design decision in business reality. A good product strategy creates a shared sense of direction, so teams know not only what to build, but also why it matters.

Enterprise vs. Consumer UX in Sustainability

IIIMPACT often works with organizations developing software for the energy transition and industrial sectors, where the people who use the tools are rarely those who choose them. This creates a unique challenge for UX design. Field operators and engineers are focused on completing their tasks as efficiently as possible. If a new platform disrupts their workflow or adds unnecessary steps, they will quickly revert to older methods such as spreadsheets or manual tracking. That is why enterprise UX must prioritize usability and workflow integration over visual novelty. Consumer-facing UX focuses on conversion and emotional appeal, but enterprise design focuses on adoption and habit formation. Understanding how real users work day to day, identifying pain points, and improving efficiency where it matters most are the keys to long-term success.

A Three-Pillar Approach for Complex Systems

At IIIMPACT, the process for developing effective products is built on three interconnected pillars: business, user, and development. First comes clarity on business objectives and measurable outcomes. Leadership alignment ensures everyone agrees on priorities and metrics. Next, the team maps users’ daily routines, identifies pain points, and ties those observations back to business goals. Finally, development constraints are evaluated to determine which features carry the highest risk or cost. Straightforward elements can move to engineering quickly, while complex or uncertain features are validated through prototypes and user testing. This approach ensures that product, design, and engineering all move in sync, balancing creativity with feasibility and reducing the costly cycle of endless revisions.

Translating a Conversion Mindset to Enterprise Tools

Although known for his work in consumer conversion optimization, Makoto applies many of the same behavioral principles to enterprise software. Whether the goal is a purchase or a workflow completion, people still respond to clarity and simplicity. Long forms and information-heavy screens may appear efficient, but often lead to fatigue and mistakes. Breaking complex tasks into smaller, digestible steps helps users stay focused and accurate. Adding guided onboarding and contextual tips enhances confidence, especially for those using complex technical systems for the first time. The real metric of success isn’t the number of clicks, it’s whether users can complete their tasks correctly and independently. By treating enterprise adoption with the same discipline as customer conversion, organizations achieve higher engagement, fewer errors, and greater return on investment.

Aligning Design and Engineering

Effective collaboration depends on transparent communication, and that is often where organizations fall short. IIIMPACT follows what it calls a “tri-track” workflow: during discovery, design leads the process while developers contribute early technical feedback; during delivery, development leads but keeps design involved to safeguard usability. This continuous dialogue eliminates the traditional handoff that often separates teams and slows progress. Regular reviews, informal check-ins, and shared visibility across disciplines replace fragmented workflows with genuine collaboration. As Makoto notes, communication is the simplest and most powerful way to prevent silos, yet it is still the hardest habit for many organizations to build.

Managing Risk and Speeding Time to Market

In high-stakes sectors such as energy or climate technology, the cost of getting things wrong can be immense. The best way to reduce risk is to identify uncertain or high-impact features early and validate them before a single line of code is written. Quick prototyping and user testing allow teams to spot weaknesses before they become expensive problems. This approach may seem like a delay, but in practice, it accelerates delivery because it minimizes rework later. Makoto describes it as taking one step back to move two steps forward; a deliberate pause that ultimately saves time and budget while producing better outcomes.

When to Invest in a Design System

A design system becomes essential once patterns stabilize and multiple teams start building within the same product ecosystem. It creates consistency, speeds up delivery, and maintains a coherent brand identity across screens and modules. However, such systems only add value if they are actively used and maintained. Teams should start small, documenting proven components and expanding gradually. Treating the system as a living product with clear ownership, ongoing updates, and training ensures it remains effective rather than becoming another outdated asset in the company’s archives.

Metrics That Prove Real Value

While traditional UX metrics like time on task, completion rate, and NPS remain useful, the most persuasive evidence of success is data that demonstrates business impact. If a sustainability platform promises faster detection or reduced operational downtime, those improvements must be measurable. Tracking metrics tied directly to ROI validates the investment in design and reinforces confidence across departments. It also allows product teams to continuously refine based on what truly improves performance.

The AI Competence Gap

Makoto cautions against overestimating what AI can do. Designers may view AI-generated code as flawless, developers might trust AI-driven design too readily, and executives sometimes believe automation can replace experienced teams. In reality, AI is a powerful amplifier, not a replacement. It accelerates ideation, research, and pattern recognition, but the quality of its output still depends on human expertise. The future belongs to teams that understand how to combine AI’s efficiency with professional judgment, using technology where it helps rather than where it simply impresses.

Lessons for Climate and Energy Innovators

“If your grandmother can’t explain your product strategy,” Makoto says, “you probably don’t have one.” The advice is simple yet practical: keep your strategy clear, measurable, and centered on real user needs. Align leadership early, design around genuine workflows, and treat AI as a supporting tool rather than a shortcut. In a rapidly changing digital environment, the teams that balance speed with direction, communicate consistently, and adapt based on real feedback will be the ones shaping the software backbone of the transition economy.