top of page
Image by Raquel Pedrotti

Tips and Tools

We know ChatGPT can (and probably does) write the majority of the content on the web today. So, we're skipping the fluff, and getting to the juicy bits. What can't AI help you with?

    • Jul 20, 2023
    • 2 min read

Defining my technology requirements

A requirement is a specific functionality or characteristic that a software or system must have to meet users' needs and expectations. - ChatGPT

Defining requirements requires analysis. You will be most successful if you can drill down to the true need versus simply note-taking on all the desires and frustrations with the current systems.


Follow these steps to get you started:

  1. What is the box. Define what kind of technology you are looking to invest in. What area of the business are you focusing on? It's possible you need to look at all of your business, but that will require a lot of analysis. So target your problem areas first, then scan the others to ensure you're not missing any significant gaps and that the new technology will fit well into your current set of systems.

  2. Talk to the users. Setup group discussions and interviews with representatives of all the teams who will use this new system. Think about who puts the data in, who needs to see reports on the data, who receives the data further in the process.

  3. Ask the right questions. Structure your questions to be open-ended, such as:

    1. What are some of the challenges with...

    2. How do you currently...

    3. What is the most time-consuming activity in...

    4. What kind of data do you like to see in...

    5. How do you like to see information about..

  4. Dig deeper. Ask a digging question at least 2-3 times to get to the root cause of the issues. Try asking:

    1. Why do you think...

    2. What do you think is the cause for...

    3. How do you think that relates to...

  5. Document the requirements. List all the requirements with a role in mind. WHO or WHAT shall be able to do this? For example "The system shall automatically..." or, "The Sales Person shall have the ability to..."

  6. Clean up the requirements. Ensure there are no contradictions, no duplication. Ensure they are organized, grouped, and clear. Check that they still tie back to the original objectives and haven't taken a life of their own into an unrelated tangent.

  7. Prioritize. Go through the requirements with a subset of users to prioritize them in a way that all agree. The simplest way to do that is using: 1-Must have, 2-If the price is right, 3-If budget and timeline allows.


Still not sure? You know where to find us. We can help with all or some of the steps in this process. We also have additional templates and tools to get you there!



Comments

bottom of page