Low fidelity wireframes in UX explained

[@stiggy-the-stig]

I work in the high tech industry (for different clients) and we start off with low-fidelity. Complex machine or service UIs have workflows that takes months or sometimes years to define, during which you often start from scratch again several times. Even if the client has a mature design system, high (or mid) fidelity is not the right approach here. I can imagine it works if you only do straight forward stuff like e-commerce or something.

[@heyhelmar]

Do you have any advice on how to identify companies like this before applying?

[@kicknight]

I have the same experience, for most complex systems lo-fi is still best approach.

[@MissFittUX]

That's exactly what he said in the video?

[@kicknight]

@@MissFittUX for a brief sec yes, but the title is misleading

[@design_lovers]

Interesting. In our agency, we try to use low-fi wireframes a lot. I taught my designers never to skip this part. We have a lot of instructions on how to keep wireframes lo-fi to focus on logic at this stage. We see the benefits of this approach.

[@MalewiczHype]

There are companies that use lofi a lot - it really depends on types of projects. We do them always when there's not enough information at the start, but most projects are actually quite simple.

[@design_lovers]

@@MalewiczHype When projects are simple, like a landing page or a single-function app interface, we usually skip the “user flow” stage. But even for simple projects, we always create low-fidelity prototypes. Of course, I understand that there is no one rule for everyone. It depends on processes and people.

[@abigwreck]

Man....as a UX content designer, this INFURIATES me, because it happens 99% of the time. So much is missed by diving straight into high fidelity, but as they say, you can't unbake a cake. I always want to start with customer journals and flows, but requestor don't want to take the time, because that requires effort from them, instead of throwing it over the wall. There's often massive heuristics issues that are missed by going straight to hi-fi, but stakeholders and eng teams don't care cuz they still view UX as a speedbump, so they just find whatever designer will immediately make visuals and go with them. Low fi generate conversation and real discussions about the correct direction to take, hi fi first is less effort, but leads to a compromised user experience for end users.

[@looksmatteronly]

That's bs

[@ProvocativeSloth]

You're very right, @abigwreck. I've consulted on a far too many large-scale projects that inevitably folded because the in-house design team jumped straight into hi-res from the off. Fundamental flaws were missed early on because no one mapped out the underlying processes. Everyone was too scared to change direction because they'd invested time, effort and resources into poorly thought out crap that looked fancy. I've found the following types of companies tend to value the UX design process most highly: - Any company that produces hardware (especially if it runs on its own operating system) - Large corporations who are quickly falling behind more dynamic competitors - Very early stage start ups (if the founder isn't a complete dick) - Established design agencies and technology consultancies - Massive orgs with enough budget to run an R&D department - Any company with a highly experienced Product lead/Tech lead that has worked in any of the above Don't doubt your process. You'll look back and laugh when you find out the company you left REALLY f**ked things up.

[@Mithferion]

When I design Dashboards, I use the low fidelity technique for myself (after I made a series of questions about what needs the Dashboard should cover), then I do a high fidelity mockup (since I create the Dashboard, I know what's possible) and that's what I show to the users; it has worked well for me until now

[@The_Wu_Zone]

I do it this way as well

[@akvilebutkute7764]

How could I learn Dashboard fundamentals?any good advices?I have made one onU X bootcamp And I would like to su dive deeper

[@SzabatDesign]

Brilliant episode! Personally, Low Fidelity Wireframes help me when building information architecture and wondering how a given solution should work and whether, for example, filters should be placed from above or better from the side. This helps me quickly visualize the solution and allow me, as a designer, to consider the pros and cons of this solution. Thanks, Michał very good episode and have a beautiful day! ✏✏

[@MalewiczHype]

We do it mostly for really complex flows that we need to be sure both us and client are on the same page with. Luckily most design is not like that, it's really simple and straightforward so we mostly do mid-hi fidelity.

[@sidiqprihatno662]

@@MalewiczHype very true. thanks for mention that

[@victim21]

Low-fi for bigger projects, hi-fi start for smaller ones. Lately I've only had one week per project, so I've been going right in to hifi because I simply don't have the time, but I can feel the frustration when the stakeholders focus on colours etc rather than the placement/flow.

[@ProvocativeSloth]

Low fidelity (aka wireframing) is just as much to stop YOURSELF from becoming attached to your design outputs too soon as it is your client. Once you've tweaked something to look production ready, youre way less likely to rip up your ideas and start again from scratch when you need to. Also, if something looks like it took a lot of effort to put together, your client and team may feel apprehensive about highlighting its flaws (if indeed they can see past the gloss and polish) Sketching and wireframing are essential steps in the design process. Whenever I encounter poor UX during a peer review or critique session....they skipped straight to hi-res "because Design System". P.s. wireframes still use actual UX copy and semantic colours (i.e. red=error, green=success)

[@MalewiczHype]

Those are some valid points but they mostly apply to the exception I did mention in the video - most flows and screen groups are easy. Repetitive. We barely get any discussion, the clients just sign off saying "all looks great here" and it just works faster. We do use low fidelity (but not sketches anymore) for very complex flows or new features even the client has trouble defining fully and there we do need their complete focus (and ours). And no we don't use a design system early on - we systemize after the initial works is done. Maybe we're lucky but we really get very little "change requests" when we finalize a design. Almost none or very miniscule ones.

[@PokeFangOfficial]

Fully agree. I can honestly say I've only used LoFi a handful of times in the past 10 years. I will often just start my design process there, but with a good understanding of the client and the user you should be able to get the prototype to 80-90% of final design on first internal review, then spend a few days in minutia with the understanding that UX is iterative and we will be optimizing it based on data post-launch.

[@suzanneshea520]

This makes a lot of sense - but I still like how you taught the text frames for planning out copy for landing pages. That is really helpful to visualize a longer screen.

[@MalewiczHype]

And it also helps a lot with marketing people as they are even more focused on colors and graphics than typical stakeholders so for them not having visuals but having right size copy is essential :)

[@debbittencourt]

I love your animations so much! Awesome content, as always

[@rajmusic1493]

You are right. I work at an industrial mnc and it is more around mid….because of design systems, quick iterations, tight deadlines

[@MalewiczHype]

Exactly the industry is becoming faster and faster. Sure - it would be better to slow down and maybe take better, more conscious decisions but we are where we are.

[@hseindesigns]

I wasn't planning on watching but the video is too short to skip! 💛

[@Lorenzo12089]

I'm a beginner at UI/UX design and wanted to ask where I can get people for interview for my case study. My case study is about designing an import/export and cargo website for my father's business. Its basically a trade and tourism company, so there is a mixture of e-commerce (people buy turkish products online or we buy for them and then sent the items to client's respective countries), logistics and courier service. Can you give me any tips as to where I should start or how I should approach it or if you know anyone that might have done a similar case study?. I'm currently looking at other websites such as dhl, ups, fedex and other logistics company (trying to identify problems) but I'm still a bit vague as to where I should really focus on my case study. Also, finding people for interview is another issue.

[@kevyn.patrick]

Can you make a video explaining about copyright and content rights, please? I'm always afraid of using premade UI KIT yk, but it seems to be so handy

[@MalewiczHype]

It differs between countries a bit and the copyright type so it's not easy for a one size fits all

[@gloriacassidy]

Yes this is very insightful. I sketch and do the basics since am still coming up.

[@MalewiczHype]

Good apprach!

[@ProvocativeSloth]

Never stop sketching. It may seem frivolous at the time, but the playfulness can spark inspiration seemingly from nowhere. Keep your favourites in a little file (unless you're required to shred literally everything). They're great to look back on once you become an ol' pro. :)

[@gloriacassidy]

@@ProvocativeSloth thank you, I will do well to continue.

[@Silhouette_one]

I've just started learning UX design and I am learning low fidelity wireframing right now lol. Is it true that low fidelity is "phasing out"? Is it a good core skill to learn?

[@MalewiczHype]

It's good to know it and know how it works - but you likely won't be using it a lot. Sometimes - yes.

[@adarshss516]

True true true we did same today nobady has time for bullshit everyone wants pretty design and helping devlopers to make it fast

[@MalewiczHype]

There are those rare exceptions where a lofi wireframe does make sense but yeah, they're very rare :)

[@effakrisma]

I agree that 100% client not sure what they want to build exactly😅

[@martinmichaelfrederiksen5820]

Skipping LoFi prototypes is often a really bad idea. However, if you are in a hurry to get to the wrong result fast, it works.

[@stevensilitonga]

I'm a beginner, how do I tell if a LFW is gonna look good later? I don't think I have the mental capacity and sufficient experience to do so.

[@paczes]

I don't agree. Whenever I show mid fidelity stuff to stakeholders or developers they pay attention to little things and give the feedback about the visual aspect of UI. So to cut off those meaningless discussions I go back to block frames on the first stages of the discussion.

[@MalewiczHype]

The thing is all in the approach and the way you present that work. We kind of got to a point where we naturally guide the clients and bounce off all miniscule detail questions. But also - as I mentioned - we use lofi for very complex flows where full attention is needed. Simpler things usually end up with barely any feedback anyway :)

[@LC-ed3ll]

I have never used low fidelity ! Alway mid fidelity. When I was at school I would create the low fidelity version at the end 😂 But a good user flow is essential to go straight to mid fidelity !

[@MalewiczHype]

There are those rare cases where low fidelity is actually a good idea but yeah - most of the time it's a waste of energy.

[@LC-ed3ll]

@@MalewiczHype of course ! When it’s web3 for example I need it because it’s to much for my brain.

[@brianvalachovic4150]

I think this is a big mistake, but there are a lot of variables. Are you trying to test a concept? Validating your understanding of a problem? If so, I'm willing to bet your discussions with customers turn into design critiques with that finished looking prototype and you miss the mark. How about Engineers? Have you included them to ensure feasibility? No? Whoops! That background image won't work with the 3rd party UI component they're using and they're going to need a few days to figure out how to override a boatload of css. See how quickly all your shiny prototype work fails? Not to mention tge disservice you do to yourself in becoming married to the design because it inherently feels "done".

[@adirmugrabi]

strongly disagree with this approach. this just causes pointless arguments about colors, button style etc... mid fidelity kills creativity, since you force everyone to see it the same as you do. rather than just get the "jist" and develop it in their head

[@MalewiczHype]

Maybe in some cases it does - we usually get barely ANY feedback from clients - 99% of the time they like what they get from us in the first iteration.

[@Core034]

fix you site