You’re starting a new R&D project. What tools do you need to create effective user stories?

Research and Development is astonishing and an amazing department in which it doesn't lean to a specific tools. Its just the passion, think and just do it.

The best tool depends on project's needs, team size, and budget. Consider factors like: -Project complexity: Simple projects might be fine with basic tools, while complex projects might benefit from dedicated user story management software. -Team collaboration needs: If collaboration is important, choose a tool that allows for easy sharing and editing of user stories. -Budget: There are free and paid options also available. We can leverage user story writing tools like Microsoft Word or Excel for basic documentation, or sophisticated options such as Jira Software. Remember to choose a tool that aligns with your project’s complexity, collaboration needs, and budget, ensuring clear, user-centered user stories for your R&D project .

I would do a quick IP landscape, to see if there is someone else doing the same. If you are doing this from a company with an IP department, probably they will have tools such as Innography to give you a better picture.

Una de las primeras lecciones aprendidas fue la importancia de la empatía con el usuario. Realizar entrevistas detalladas y encuestas ayudó a profundizar nuestra comprensión de las necesidades y expectativas de nuestros usuarios. Utilizamos Google Forms para recopilar datos y herramientas de IA para analizar sentimientos en redes sociales.

I use the concept of delight thinking. It does not start with a need or an issue. It sarts with providing people 'Unknown Unknowns', products, servives, but especially experiences people didn't realise they could get. This way we create experiences close to magic, but still real. It's like when I give you a present from your bucketlist for your birthday, you're happy. I I give you a present you didn't realise you could get, you're super happy. That how innovation starts and gets adopted.

Collection of all type of data is necessary for user stories. Various type of surveys, interviews and analytical tools which is necessary to provide a wealth of information. This data provide the exact direction where your R&D project addresses. By analyzing user feedbacks, you can ensure that project is ready for user needs.

One of the most challenging tasks in conducting UX research is harmonizing quantitative and qualitative data. A quantitative approach has the advantage of easily identifying patterns based on mathematical and statistical models, with a higher possibility of minimizing the researcher’s own subjectivity. A qualitative approach adds a human, more personal dimension, informed by our own life experiences and our capacity to empathize with others' experiences. Both approaches offer different insights that complement each other and can help identify impactful solutions when interpreted appropriately.

A lot of data people are not willing to share. But when the advent of new way to store and share data using data vaults on a new version of the internet (the tech is called SOLID), I believe this is about to change.

Collect as much data possible via interview, or online surveys (survey monkey) while documenting user profiles, locations, cultures, gender, race etc.

Aus Sicht der Forschung und Entwicklung bringt das mehrere Vorteile mit sich: - Es werden relevante Probleme identifiziert, an denen gearbeitet werden muss. - Die wichtigsten Funktionen k?nnen priorisiert werden. - Die Produktrelevanz für die Nutzer steigt. Eine kontinuierliche Verbesserung wird erm?glicht. Insgesamt ist das Einbeziehen von Benutzerdaten entscheidend für den Erfolg von F&E-Projekten. Es hilft, die richtigen L?sungen zu entwickeln und eine hohe Nutzerzufriedenheit zu erreichen.

The importance and feasibility of a user story will first depend on our goals. This does not mean we have a fixed solution in mind for a specific problem, but rather, what is the ultimate objective, the transformational change we want to leverage in a system? When prioritizing, the analysis should be guided by how the potential user stories lead to or contribute to this desired change. HINT! Consider the answers within the complexity of the systems we are analyzing...Complexity is a key concept here.

- Das MoSCoW-Modell is'n echt nützliches Tool, um Anforderungen zu strukturieren und zu priorisieren - Für F&E-Teams ist es wichtig, die knappen Ressourcen effektiv einzuesetzen -Mit MoSCoW k?nnen die allerwichtigsten "Must-have" Funktionen identifiziert und als erstes umgesetzt werden - Das hilft, den gr??tm?glichen Nutzen für die Endnutzer zu schaffen und die Entwicklungskosten niedrig zu halten - Ein Priorisierungsrahmen erm?glicht auch 'ne transparente Kommunikation mit den Stakeholdern Insgesamt also echt empfehlenswert für F&E, um die - Ressourcen geschickt zu nutzen und die Kernbedürfnisse zeitnah zu erfüllen

Try the effort-impact matrix to identify high-impact, low-effort wins for user stories. These quick wins build momentum and user trust. More complex projects? Consider the MCDA approach, which factors in cost, risk, and potential benefits. Remember, user stories should reflect these priorities. Focus on stories that address high-impact user needs with achievable development efforts. This ensures your R&D delivers value quickly.

Eine immer noch bew?hrte Methode zur Kategorisierung und Priorisierung von Anforderungen ist das gute alte KANO-Modell mit den Kategorien: Basisanforderungen, Leistungsanforderungen und Begeisterungsanforderungen.

Es fundamental la priorización. Para ello, antes de nada tienes que ver todo con perspectiva para identificar lo que es útil y lo que no en base a un objetivo claro. Nunca perder el objetivo de vista.

La colaboración eficaz no sería posible sin el uso de herramientas adecuadas como Slack y Microsoft Teams, google meet, zoom, ahora estoy conociendo clickup. Independientemente de la app que se utilice lo importante es la comunicación y que se consiga llegar a conclusiones en las reuniones.

It is important to consider the make up of the team when creating these stories. Having a cross-functional team is extremely critical to being able to capture diverse perspectives and viewpoints. User stories resonate differently with people of different educational and work backgrounds. A team made of only scientists and engineers will most likely capture only selected facets of the user experience, and this might lead to overlooking others. Having members with diverse backgrounds from marketing, advertising, sales, design, etc., will help to not only generate a diverse set of ideas, but also ensure that you are getting a high-fidelity view of the space your users are “living” in.

Collaboration tools are essential enablers for teams to effectively discuss, refine and align on the optimal set of user stories to tackle. Some key tools that can facilitate this process: Project management platforms (Jira, Trello, etc.): Maintain prioritized backlog of user stories Allow collaborative editing, discussions and updates Associate user stories with requirements, tasks, owners Virtual whiteboards (Miro, Mural, etc.): Visually map out user journeys and draft user stories Collaborate simultaneously with digital sticky notes Facilitate virtual ideation and storymapping sessions

Collaboration tools are the technological backbone that supports the joint efforts of R&D teams. They facilitate communication, project management, and information sharing, allowing team members to work together seamlessly, regardless of their physical location. These tools range from simple document-sharing platforms to complex real-time collaborative environments, ensuring that every team member is on the same page and driving the project forward in unity. In short, collaboration tools are vital for synchronizing the collective talent and energy of R&D teams.

Whiteboard or Online Whiteboard: A physical whiteboard or an online collaborative whiteboard tool like Miro or Mural can be great for visually capturing ideas and user stories during brainstorming sessions. Mind Mapping Tools: Tools like MindMeister or XMind can help you visually organize your thoughts and explore different facets of the user experience.

One thing I've found helpful in story mapping is the use of visual aids to represent the user journey. By creating a visual storyboard, team members can better understand the flow of the user experience, identify gaps in the narrative, and prioritize features based on user needs. This method fosters a shared understanding among stakeholders and ensures that the final product aligns with the users' expectations and desires. Story mapping is a powerful tool for transforming abstract ideas into concrete plans and actions in R&D projects.

Should be part of Design Document, that identify evolution of products, mapped to user experience, technology availability, cost etc

Gerade bei der agilen Entwicklung physischer Produkte sind Story Maps unverzichtbar. Sie zeigt Abh?ngigkeiten auf, erm?glicht die zeitliche Zuordnung von User Stories und damit auch eine l?ngerfristige Etappenplanung ?hnlich dem PI-Planning bei SAFe.

Story mapping is an excellent technique to provide structure and ensure cohesion across the different user stories being developed. The key steps involved are: Define the User Activities/Goals across the top row - The higher-level jobs users are trying to accomplish, representing the narrative flow. Capture User Stories underneath each Activity - Specific stories capturing the steps, scenarios and requirements needed to enable that activity. Prioritize the Stories vertically within each Activity - Higher stories should be completed first to realize basic functionality for that activity.

Story Mapping ist echt hilfreich für Forschung und Entwicklung: - Zeigt den gro?en Zusammenhang der Nutzergeschichten auf und hilft so, Lücken in der Nutzererfahrung zu finden - Erleichtert die Priorisierung und Planung im Entwicklungsprozess - F?rdert den Austausch und die Zusammenarbeit im gesamten Team Insgesamt sch?rft Story Mapping den Fokus auf den Kunden und verbessert die Planung und Kommunikation. Das kann entscheident für den Erfolg von Produktinnovationen sein.

Incorporating continuous feedback is essential for refining user stories and ensuring they remain relevant. Tools like UserVoice, SurveyMonkey, and feedback features in collaboration platforms enable ongoing user input and iteration. Regularly gathering feedback helps identify areas for improvement and validate assumptions. This iterative approach ensures that the user stories evolve based on real-time user experiences and insights, leading to more accurate and impactful outcomes in the R&D project.

Continuous user feedback loops are absolutely vital for keeping user stories relevant and ensuring the R&D efforts remain tightly aligned to real user needs over time. Some key tools and methods to enable this: User testing tools (UseResponseBatch, UserTesting.com etc.) Get moderated/unmoderated feedback on prototypes and betas Identify usability issues, validation of assumptions Prioritize improvements based on observed pain points

Let data lead to the conclusion. Recalibrate of the outcome is necessary, if not enough data is collected. Do not rush to conclude with minimal data in hand.

Soliciting feedback encourages collaboration and involvement among team members, and possible end users, resulting in richer insights and more imaginative solutions.

- Aus Sicht der F&E ist es wichtig, eine offene Kommunikation mit den Endnutzern zu pflegen. Je mehr man über deren Erwartungen und Herausforderungen erf?hrt, desto besser kann man darauf eingehen. - Die gesammelten Erkenntnisse helfen auch dabei, das Verst?ndnis für die Zielgruppe zu vertiefen und die Entwicklung in die richtige Richtung zu lenken. So l?sst sich Ressourcenverschwendung vermeiden. - Allerdings muss das Feedback sorgf?ltig analysiert und priorisiert werden. Nicht jeder Vorschlag muss umgesetzt werden. - Insgesamt kann kontinuierliches Nutzerfeedback dazu beitragen, dass das Endprodukt den Bedürfnissen der Zielgruppe entspricht - was entscheidend für den Erfolg eines F&E-Projekts ist.

begin with an end in mind but allow diversions, change process, milestone shifts to evolve into what is required by end user. (tangible end product, application, dissertation or technical study assessment). Its a mutual pathway whereas tools and maps are enablers that keep everyone in the project sane (??)

Well, that's the wrong question to ask. No tool can magically create effective user stories for you. The question is, rather, what do you need to create effective user stories? The answer to that question is the right mindset. You need to want to create better user stories because you believe this is the path to customer satisfaction and business success. With that mindset, you'll find ways to obtain the necessary knowledge and skills. And that's it. Once you are there, you can see which tool might best support you. Hence, start with the mindset, not with the tool.

There are many tools for R&D in the real world, but there is no perfectly applicable tool. The important is attitude. It is a matter of thinking about a polite and sincere attitude with humility. Which tools affected good outcomes doesn't matter. If you want to achieve successful outputs and outcomes you ought to believe that saying 'Honesty is the best policy.' R&D is the action for evolution to the future. Therefore, Human beings have to be sincerely acted and never forget humility. R&D is a huge project and no one can do it himself/herself alone. It would be done by collaborating with many stakeholders and workloads.

In my view, you need a combination of a) technical tools ( collaboration tools (Slack, Google Workspace), project management tools (JIRA, Trello), documentation tools (Confluence, Notion), visualization tools (Miro, Lucidchart), user story mapping tools (StoriesOnBoard, FeatureMap), b) the right mindset, c) the right team for this particular R&D project, d) passion and finally e) keep b, c and d throughout the entire process.

Es importante la retroalimentación de tu equipo de trabajo en todas las etapas del proceso de recolección e interpretación de resultados. Además, uno debe saber identificar que herramientas estadísticas o de visualización se pueden utilizar para ofrecer información visualmente sencilla que podría parecer compleja. Herramientas como Tableau, Originlab y algunas librerías de python me han ayudado con mi trabajo.