¿Cómo recopilaría los comentarios de los usuarios para definir los requisitos funcionales?

In a nutshell, this is part of continuous product discovery; the first iteration is always challenging but with over a period of time one would be able to refine the product features. A few approaches that have helped me and these should be taken in collaboration rather than stating one is better than the other. 1. JTBD - Jobs to be done framework.. it helps one to map the user activities across the product lifecycle. 2. User journey maps. It covers the entire flow. 3. Market scan for continuous benchmarking. There are enough sources in the public domain what has been done by the leading institutions in your industry across the world.

In my experience, the best method would be the interview followed by ratification by functional specification, this way you can actually hear and feel the client's desire in relation to the demand.

I always like to get what the industry calls, "The Voice of the Customer" There will be all the people that actually take time to complain or identify a problem and need company to resolve. Also need all those silent sufferer customers that try and find an answer through self service or Google. Finally I gather all data and then interview front line Support teams and product teams. I vet and parse together information from multiple sources. I then vet out details in phone calls "recorded" and emails and ensure we identify all key issues. GPT can help out a lot on all this including also using your powerful CRM data.

Crafting a feedback strategy starts with pinpointing your project's mission: Identify the issue, understand your audience, and their challenges and aspirations. This clarity guides your feedback aims and metrics. Choose the right crowd for insights, deciding on the best approach and tools—surveys, interviews, focus groups, usability testing, or prototypes—to align with your project's scale, budget, and deadlines.

Collect user feedback to define functional requirements. Observe user interaction with the current system and analyze customer support feedback.

Activating your feedback strategy means engaging with participants ethically and effectively. This involves recruiting them clearly, preparing materials thoroughly, and conducting sessions with openness and empathy. Always ask open-ended questions, listen actively, and respect privacy and consent laws. Remember, a genuine 'thank you' goes a long way :-)

Good companies invest in their employees and let them give you feedback. Get the feedback from them. Identify what's wrong and what are their biggest pain points? If it's hard for the team to solve, then its a nightmare for most customers. Identify workflows and create a visual roadmap and journey of what are the problem points that you can solve. I then take this to a stakeholder team and feed them with neutral data to prove with data integrity that the issues are not biased. From there listening and setting up a plan of attack is next step.

You can also use in-product Research with Sprig. Then you need a solid repository like Dovetail or even a simple doc tool like Coda 💎

Com sua estratégia definida, colete e armazene os feedback´s. Grave a reunião, transcreva os audios... Mas sempre tenha em mente que ouvir atentamente e empaticamente é o que eles esperam de nós. Seja ético e correto.

Decoding user feedback is like solving a puzzle. Organize, categorize, and analyze to uncover patterns and insights. Craft personas and journeys from these clues to shape innovative requirements. It's about turning raw data into a roadmap for groundbreaking improvements.

Junto com os usuários chave, analise e valide tudo. Cubra todas as brechas e lacunas usando sua experiência e tente antever as necessidades do seus clientes.

Use clear and concise language when writing functional requirements. Avoid using jargon or making assumptions. Prioritize and group requirements based on importance, dependency, or complexity. Validate requirements with stakeholders, such as users, clients, or developers, to ensure accuracy, completeness, and feasibility.

Os requisitos funcionais devem ser únicos e sem ambiguidade. Priorize e agrupe os requisitos afim de identificar reuso e valide com seus usuários, clientes e envolvidos.

Utilize a format to express a feature like "As a [role], I want to [action], so that [benefit]". This ensures clarity. Organize requirements with a method like MoSCoW to categorize and prioritize the requirements. This helps in focusing on what's essential. Regularly review the requirements with stakeholders like users, client AND developers to ensure they align with expectations and are feasible. This is crucial for verifying the accuracy and completeness of the requirements. Recognize that requirements evolves. Be open to revising them based on ongoing feedback and testing. This iterative process ensures that the project remains aligned with user needs and market demands.

I usually gather user stories and actual use cases so that people can resonate with the source of the problem and by journeymapping everything in a non-technical way. Everyone at the table will understand the problem you are solving for and the technical people (Dev team, QA, and Engineers) will understand what the heck you actually need so they know how to program it correct. If you don't do something like this you may miss the boat all together. Believe me I've worked for the best Silicon Valley companies and see more costly mistakes than ever by not following this simple path to success. Once you have all this gathered, use the common industry formats. There are tons of examples of this already noted. Use it. This is needed.

In the fluid world of system development, functional requirements aren't set in stone and they're living entities that evolve as feedback flows, designs pivot, and technical landscapes shift. Embrace this dynamism by wielding the power of a robust requirements management tool, be it sophisticated software or a meticulously organized spreadsheet. This isn't just about storage; it's about creating a transparent, accessible record that adapts in real-time, ensuring every stakeholder is aligned with the project's beating heart. Remember, managing your requirements is akin to navigating a river and stay responsive to the currents of change to reach your destination successfully.

Clearly documented requirements keep all developers, designers, and QA testers on the same page and working towards the same goal, avoiding misunderstandings.

Requisitos funcionais mudam, por isso é importante gerenciá-los. Mantenha a documentação em dia e sempre opte por uma documentação simples e direta. Quaisquer alterações devem ser documentadas e alinhadas com o escopo e objetivo do projeto.

Some of the best Silicon Valley Leaders in the industry require a lot of reviews even on quick agile projects and programs in product. This allows us to make iterations and to make sure we continue to adapt as we go. If you follow this methodology, you'll have several happy customers and end users not just a happy executive that signed off on the big budget that you promised them gold but delivered a tin can.

You can also anticipate user future needs and tech advancement when taking into consideration defining functional requirements so that the product remains relevant and adaptive over time.