Marina Krutchinsky

Let's look at the example of adapting UX timelines for a healthcare app. First, we could focus on simplifying appointment booking -> a critical feature for users. Then, we would implement bi-weekly reviews with the team and stakeholders -> to assess progress and user feedback. Also, we would utilize agile development cycles for rapid iteration based on customer feedback. This approach would keep the project aligned with user needs and business goals, while preventing scope creep and ensuring it stays on track and budget.

To me, risk-taking in product design isn't just about introducing new ideas, it's about flipping the script on what we think familiar products should/could be. Take Apple's bold move with the iPhone -> remember how they ditched the physical keyboard in favor of a multi-touch interface? Back then, it seemed like a wild gamble. But look what happened! It completely changed the game for the smartphone design industry, making touchscreen interactions more intuitive and user-friendly. Where are physical keyboards on phones now? They're (mostly) history. This just goes to show, taking that leap can redefine an entire industry, pushing the boundaries of what's possible.

In my experience, involving users in developing IA is about turning them from audience to co-creators. When you get their input through things like card sorting (which is a really insightful exercise for seeing how they categorize information), you're not just guessing how they group and relate concepts – you're actually hearing it from them. This way, everything from the initial concept to the final product is shaped by real, live user feedback. That's what involving your users does – it makes them part of the story and ensures your IA system isn't just functional, but also a match for the mental models of the people who will be using it.

What I've found helpful is a structured, two-phase approach for balancing innovation and practicality in defining goals and scope for prototyping: Phase 1: Research Review - Compile all current research related to the project. - Separate between what is already known (user behaviors, market trends, etc.) and what needs further exploration. - Use this verified knowledge to build a strong, fact-based foundation for the prototype. Phase 2: Rapid Testing - Prioritize key hypotheses for testing. - Create quick, iterative prototypes. - Conduct user testing early. - Continuously refine based on feedback. This approach ensures that the prototyping is guided by both existing knowledge and ongoing learning, making it both innovative & practical.

For remote work, I'm a huge fan of the well-thought out async design process. Here's my approach: - "Document-driven" discussions: shared documents for brainstorming -> allowing time for thoughtful contributions. - Pre-recorded updates: brief video updates replace live meetings -> saving time and fitting everyone's schedule. - Async design reviews: designs posted in shared spaces for feedback at team members' convenience. - Using tools like Trello for progress tracking and task updates. -"Office hours" (scheduled on as needed basis): live Q&A sessions for urgent or complex discussions. This method respects various schedules and fosters effective, thoughtful work.

One of my mentees felt stuck in her career. She was unsure of her "unique value". Through guided self-reflection, she revisited a number of past projects where she effortlessly united divided teams. Until that moment, she had taken it for granted, thinking, "Doesn’t everyone do this?" But no, her natural ability to bridge gaps, empower people, and create unity was her unique strength! By recognizing this, she shifted her career towards leadership roles that leveraged her gift. Just like her, taking time to think about what YOU are good at, can lead to finding jobs you didn’t even know were perfect for you!