# Build something someone can use

By Keith Azodeh, Principal AI Consultant, Asaday Consulting

1. **Name the friction.** Choose one person, one repeated task, and the result they need. Write down how they handle it today.
2. **Map the information.** Identify the records, tools, permissions, and original sources the workflow depends on.
3. **Build a small working path.** Connect one input to one useful output. Ask AI for bounded changes. Read and understand the important code before relying on it.
4. **Verify the important steps.** Check source records, invalid inputs, permissions, errors, and whether saves reached the server. Include a recoverable failure path.
5. **Put it in someone’s hands.** Watch a real person use it. Notice where they hesitate or get stuck, then improve that step.

Before expanding: can someone complete the original task, inspect the result, and recover from an error?

## Follow the example

- Product: https://afrotech.guide/
- Engineering case study: https://asaday.co/projects/afrotech-directory
- Build story: https://asaday.co/blog/keith-azodeh-afrotech-directory-data-to-product
- Connect: https://www.linkedin.com/in/azokei/
- Work with Asaday: https://asaday.co/enterprise

AfroTech.guide is an independent community-built resource.