Hello learners!
Welcome to the 20th lesson of the series 30 Days of PM by Crework! As we discuss design, it’s important to discuss wireframes because as a PM, you interact and convey your ideas to the designers using wireframes.
But before we start, make sure you are subscribed to us. In case you are not, subscribe to us right now and complete the challenge.
What is a Wireframe?
A wireframe is a 2D visualization of a digital product, ranging from very basic pencil sketches to fully interactive digital designs.
Wireframes can be static and very simple layouts of ‘what goes where’, and some may be more interactive and more closely mimic the functionality of the final working product.
Here’s an example of a wireframe that shows a page for a product on a shopping site.
This wireframe gives a good idea of what elements should appear and where they should be laid out on product pages for a store.
However, some of these interface elements trigger actions. Add to Cart, is one obvious trigger here. You need to explicitly specify for your team what happens when the user triggers that action. To do that, typically a product designer might wireframe each changed state, as the user steps through the checkout task.
When and how do Product Managers Use Them?
Product managers are also people with ideas, and sometimes you’ll need to bring them to the team. Imagine you wanted to include a straightforward user story in your next sprint—say, a signup form for a free trial of your software. Which of the following options do you think your product management team would prefer to have up on the screen as you walked them through this story?
Story Overview 1:
Simple sign-up form on a standalone page.
Keep fields to a max of 5 (including “confirm password” field)
Fields should include: full name, email, company name, password, and confirm password
Should not include any optional fields
Include a “sign in with Google” option
NOTE: Email address field should require a business domain; if the user enters Yahoo! or Gmail or other consumer webmail, trigger popup citing the corporate domain requirement. Do not allow the user to continue until entering a satisfactory email address.
The field should contain a question mark to the upper right, which the user can click to bring up a popup window explaining this rule.
NOTE: The password field should include a question-mark sign to the upper right, which the user can click to bring up a popup window explaining the rule for passwords, which should be minimal and require only a minimum character count —no special characters, capitals, etc.
Story Overview 2
You would still want to write out the logic and requirements behind this visual story. And you should have those details handy when you walk your audience through it. But wouldn’t this second option be clearer than a long text narrative?
When working with your designers, wireframes are the most common communication tool as you’re working towards a prototype or an MVP. They’re visual aid to help designers and product managers understand what’s being discussed. The better you’re able to work with wireframes, the better that thread of communication between you and your designers will be.
Day 20 - Completed ✅
Congratulations on completing the twentieth lesson of the series. 🥳
Now, you know what to do. Share your learnings with the world and be accountable.
If you have any feedback, please share it with us. We would love to have your suggestions and improve our future content for your better learning.
If you want to join a community of product aspirants where we discuss product management topics and case studies, you can join it here:
References: