So I'm currently enrolled in the CareerFoundry UX course and what they have you do as part of the lessons is to create a task or project management app called "Taskly" (You don't go so far as having it actually coded but you do go up through prototyping, visual design, even some A/B testing of your proposed design for the app)
What I'm wondering is WHEN in the "real world of UX" wireframes should actually be created because in my course I can't decide if they are having us do wireframing too early in the process. Here's what I mean:
What I'm finding is it doesn't make much sense to wireframe screens UNTIL you understand the workflow, simply because you don’t know what’s needed on screen and what’s not. Yes the course has taught us to understand first the business requirements, the users, competitors etc but then we jump right into designing wireframes and/or paper prototypes.
For instance I’ve found, for Taskly, you really need to understand how things like projects and tasks relate to each other before you can design the appropriate screens.
On the other hand wireframing screens early in this course has led me to better understand how I need Taskly to work so, bottom line, I could see in the real world doing many rounds of wireframing (iterative) until the flow makes sense enough to bring it into a protoyping program and start having users play around with it and give feedback.
Perhaps doing multiple rounds of wireframing is inefficient or maybe its unavoidable - what do you think?