UX Designers rarely do wireframes - Beginner Course part 2

[@Puleczech]

Completely agreed. Finally someone has said it out loud. I've ran into problems with wireframes in a way that they tend to be perceived as a 90% ready thing by the PM. The "just do the colours and we are done" kind of thing. While in reality you have to tackle many other problems that wireframes couldn't account for in regards to the UI design. Which definitely does not amount to the 10% of the time remaining... The more problems you try to account for (making clear how menu is structured instead of just saying "menu here"), the more time it takes to think and make the wireframe, which is in contradiction of the "wireframes are fast" ideal. Perhaps it's more of a problem of the (particular) PM not understanding the full scope rather than of the wireframe itself. But wireframes just give out a fake illusion the work is nearly complete while it is really not.

[@natalie-taylor]

Hahaha - scribble boxes! Thank you, this is great, and you called it, the tools today are so much more advanced. We will rarely show a client a wireframe because it often confuses them and adds time to the project. They think they need to see them because they heard somewhere that they should be reviewing the material at that level. Most normal people not involved in the field go derp (I don't get it) because it's not what they do for a living.

[@MalewiczHype]

Glad it was helpful! 2009-2011 was the time when this bad practice of dishonest ux work was the most rampant, now most customers understand enough not to pay for stuff they won't use or need :)

[@thearaav6670]

Brother, you are the one who talks about the truth about wireframes.. Thanks...

[@MalewiczHype]

I appreciate that

[@rathankumar9853]

@Malewicz Thanks for sharing your process in detail. One small comment. I think this videos is added twice on your Become a designer playlist.

[@MalewiczHype]

Thanks, should be fixed now

[@sprintwithcarlos]

Totally agree: I hate wireframes since there are just a waste of time. But agencies can’t afford losing these billable hours in the short term. It’s shameful

[@MalewiczHype]

Good thing is that this is changing now in a big way towards faster, more agile and systemic approaches so wireframes are now practically gone.

[@marcelstaiger9100]

@@MalewiczHype do I need wire frames in an interview for a job then? Because that is what I heard... Also I heard it needs to be part of case studies or portfolio. But I don't know... Should I invest time practicing and incorporating wireframes into my case studies?

[@majidtahiri8971]

nice video! if you can make a video showing how you build your designs step by step, that would be awesome, I have a good ux design set of skills and I know quite good stuff about ui design, however when I wanna start a new project I feel overwhelmed and I get stuck in the early phases of design

[@MalewiczHype]

thanks! We have a plan of some videos like that closer to the academy launch, the basic ones will then appear on this channel.

[@leunasmas]

Actually wireframes are getting traction especially in an agile environment where they can communicate the layout, structure of the app or website in a very quick way. People with little to no knowledge of UX tend to think of wireframes as a waste of time, but in reality they are supper useful.

[@MalewiczHype]

My point was that they used to be useful, but now with design libraries you can build high-fidelity wireframes much faster with just drag & drop so there's no need for those "classic low-fidelity ones".

[@leunasmas]

@@MalewiczHype Yes Indeed, design libraries definitely are helpful for building hi-fi wireframes, but may not be useful all the time especially when it comes to a very niche requirement. My point of view is that iterating a hi-fi prototypes or wireframes becomes a pain when there are a lot of iterations. It is less painful to create and get approvals from clients using quick wireframes. Once approved, working on the final deliverables becomes less stressful.

[@alexbramwell1870]

Wire-frames are about 'conceptualising'. You don't always have a design system or library for fresh projects/clients. Or, what about adding new components to that library... you need to create concepts. Those concepts are more often than not sketched out via the wireframe. It's up to the designers discretion on wireframe fidelity. One size doesn't fit all. Pick the correct tool to use from your kit, but don't get complacent with that pre-exisitng library. You will stagnate if you don't conceptualise from time to time!

[@beatrizmaia7721]

Btw! I'm viewing these videos through your "Become a designer" playlist and you have the wireframes video repeated in it. Just a heads up. Keep up the great work!

[@MalewiczHype]

Thank you, fixing it now!

[@madarauchiha5433]

Wireframes are useful to get the client thinking about the content and the flow of the page

[@MalewiczHype]

Low fidelity still confuses most clients and you can use a flow diagram to show the flow :)

[@madarauchiha5433]

@@MalewiczHype I agree that low fidelity confuses clients but I also believe that Mid fidelity wireframes are better if you want the client to see the content and structure so that they can provide the copy. What are your thoughts

[@MalewiczHype]

Yeah, but in many cases you can do almost high-fidelity just as fast as mid-fidelity :)

[@henkegiaretta]

I think there is a place for wireframes, because as soon as you bring in design into testing face then the focus can shift to design critique. Not always but sometimes 🙂

[@oded1310]

Hey, videos number 4 and 5 are (UX Designers rarely do wireframes - Beginner Course part 2) are duplicated.

[@dedrox3d491]

Amazing work sir✌🏼. Can u make a vedio talking about why design is not a waste of time. Im just confused about design itself

[@motasher7782]

Hello Malewicz Your 4th and 5th Video for " UX Design Basics using simple language-Wireframes " are same... Anyway your Crash Coursh is good... Keep it up...

[@MalewiczHype]

Thank you, I'll fix that soon

[@iliasmiliadis]

How can I be a member ,to watch all your videos

[@MalewiczHype]

We're adding all member videos to hype4.academy PRO plan, you can just register there.

[@marcelstaiger9100]

The potato made my day. Do you recommend a clickable prototype directly or do you still create hi fi wire frames before that then?

[@MalewiczHype]

We always do high fidelity prototypes, low fidelity is a really bad idea for user testing.

[@banefulbty]

Like everything it depends, I like to use mid fidelity when I am creating a new pattern or feature. It allows me to get the right kind of feedback from external teams. Showing high fidelity encourages people to loose focus and start critiquing visual elements

[@MalewiczHype]

I thought the same about high fidelity and "visual critique" but it's not really happening as much with mid-fidelity when it's clear it's a template interface (simple enough) - and with low-fidelity there's a bias of "what an ugly design" that people think even when you explain it to them. It's easier to "feel" how something works when it's closer to how it looks - at least from my experiences.

[@soulvani]

In agile methodologies wireframing is just waste of time.

[@MalewiczHype]

exactly. the world is moving away from wireframes, I mentioned in the video they’re mostly a relic from the past :)

[@szeredaiakos]

Well... design in the shit-design paradigm... ahagrgr .. Misspoke... I mean flat-design. yeah .. A complete design in the flat-design paradigm is practically wireframe.