I tested my original wireframe using a script that I read out loud to each participant. I watched as they followed my instructions, and I gathered some helpful feedback.

After testing my wireframe on three college students, I learned there were lots of changes I could make to my site idea that would help users decide where to click and navigate to. 

My main takeaways from the experience:

 

1. higher fidelity prototypes lessened confusion dramatically.

2. If you don't want a user to focus on something, you should obscure it. (In may case, I grayed out a few elements).
3. Calls to action should be moved to places, like the header, where they can get more attention.

​

Next Steps:

 

If I were to continue this project, I would take several new steps:

Step 1: Learn more about API documentation so that I can better design the UX.
 

Step 2: Use a different tool. I would use tools that were better with creating functional prototypes and that facilitate better user tests.
 

Step 3: More research
Perhaps, prior to step 2, I might also consult experts in the field to see if they know of existing widgets and platforms that could help give my app functionalities that I hadn’t thought of yet.

​

Step 4: Design
 

I might hire a designer to help me with the colors on my website because I’ve been told I have unconventional taste in this regard!
 

Step 5: Content Strategy
 

I would keep my content strategy pretty limited on this site because it is really a supplement to existing API documentation courses, but I think a blog and social media presence would help me network in the API doc community.