Need some inspiration for your digital strategy or website, but don't have time for reading endless posts? Struggling to keep up with the latest innovations in web design, user experience and service design? These bite-sized digital insights from UX designer and consultant Paul Boag will keep you up-to-date. Typically only a few minutes long they are ideal listening when on the move.
Podcast hosts
No host has claimed this podcast yet, if you are the host you can verify ownership by claiming this podcast
Keywords
© Boagworks Ltd
Digital Insights
Read more
Reviews
No reviews yet
Podcast information
- Amount of episodes
- 602
- Subscribers
- 0
- Verified
- No
- Website
- Explicit content
- No
- Episode type
- episodic
- Podcast link
- https://podvine.com/link/..
- Last upload date
- May 25, 2023
- Last fetch date
- May 28, 2023 12:05 PM
- Upload range
- WEEKLY
- Author
- Paul Boag
- Copyright
- Boagworks Ltd
susbcribers
- Know When to Shut UpHello again, So I recently had a fascinating discussion with one of the people I coach. She works as a UX designer for an agency and was asking about how she should handle situations where she believes terrible decisions are being made. She struggles to balance speaking up and knowing when to accept defeat graciously. It is a topic I touched on tangentially a while back, but I wanted to discuss it more directly today because I believe it is a balance many people struggle to get right. It is certainly something I struggle with myself. Some people fail to speak up because they lack confidence, while others must learn when to keep their mouths shut and let things go. I will let you guess which category I fall into! You Don’t Know the Whole Story I have learned over the years that I don’t know as much as I think I do, and any decision probably includes many more factors than I am considering. For example, the user experience must always be balanced with factors like business objectives and return on investment. It is not as simple as always going for the best experience possible. If that were the case, every company would give away their products and services for free! Different Perspectives Need Consideration Each stakeholder will come with their perspective based on their understanding of the project. Each will only see a part of the puzzle, so disagreements are inevitable. Testing is Not Always the Answer As I have said many times over the years, I prefer to test when these issues arise to decide which approach is best. However, that is not always possible due to time constraints, budget, or the nature of the issue. We Must Respect the Decision of Leadership That is where it falls to leadership to make the final call, and it is okay if they don’t always agree with you. However, we must learn to accept their decision even if we disagree. Does that mean they will always get it right? Absolutely not. However, ultimately a decision needs to be made and they will have the broadest perspective of all the factors involved. Our Responsibility That said, we have a responsibility too. Our responsibility is to communicate our opinion as clearly as possible and back it with as much evidence as we can gather. But it is also our responsibility to shut up and accept defeat if we fail to convince leadership. Continuing to argue will damage the project, undermine relationships, and is extremely unlikely to change the outcome. That is not to say you need to agree with the decision. Never say that you think something is correct just because somebody else says so. If you do, you will get sucked into the blame game if things go wrong. So instead, agree to disagree and implement their final decision with no more fuss. Don’t Take It Personally However, most of all, I would encourage you to be more laid back about whether a client or boss implements your idea or not. Your job is to present the options and give them your opinion and any associated evidence. After that, it is down to them. If they reject your idea, focus on getting better at communicating your opinion next time. Never take it personally. Ultimately life is too short, and you will be constantly unhappy if you consistently fight colleagues and management.0 comments0
- I’m Going to Contradict MyselfToday I will show you why you shouldn’t take me (or any other supposed expert) too seriously. I will contradict myself entirely and, in doing so, show you how context is everything. But before I do, can I be honest with you? You are not supposed to say things like this because you want everybody to think you are in high demand. However, the current state of the world means I am light on work. So, if you need some consultancy, coaching, training, or help to improve your conversion rate, drop me an email. I’ll even throw in a 10% discount if you book in October. I Often Ignore My Preferred Approach Not too long ago, I shared with you my preferred approach to developing digital services. An approach that began with a discovery project that crucially includes user research. I have even written about what you should do as a minimum in this type of user research. However, if I am being honest with you, I often ignore my own advice. Blindly following best practices can often be wasteful and less effective in delivering results. Let me give you a real example, hopefully explaining why you should always favor common sense and your judgment over what you see online. I have been working with a company for some time now, helping them improve the conversion rate on their website. Because of a change in circumstances, we concluded that the site needed to be redesigned and rebuilt. I am not usually a fan of this approach, but it was the most cost-effective in this case. Sometimes I Do Things in the Wrong Order Typically, I would start with a discovery phase to better understand the user, understand the competitive landscape and speak with stakeholders. However, I decided against that, jumping straight into prototyping. I didn’t even do any card sorting or top task analysis to decide on the information architecture. My reasoning was I knew this client, their audience, and their needs well enough to have an initial stab at the website. Of course, I am making many assumptions, and I may well be wrong. But I intend to conduct my interviews and user research retroactively rather than upfront. I Occasionally Carry Out Research Retroactively If I had begun the project by interviewing stakeholders and users, I wouldn’t have known what to ask them. So I would have done it to go through the motions rather than because I had burning questions. However, prototyping has thrown up various questions in my mind that I can now address through user research. Moreover, showing the prototype to users and stakeholders will undoubtedly generate even more questions or wrong assumptions on my part. It makes a lot more sense to carry out the user research at that point when I have specific issues I need to resolve. Don’t Do Things Just Because You Are Supposed To! What I am driving at is that too often, we do these exercises because that is what we are supposed to do, not because we have a clear idea of what we want to learn. Everything from customer journey mapping to user surveying are tools that help us answer questions. If you don’t know what questions you need to ask, then don’t use them until you do. Use these techniques when it is sensible, not just because somebody told you to in an article.0 comments0
- Working With Others Is ToughHello again, I have found myself thinking a lot about working with others recently. Digital requires us to do that a lot. We work with designers, developers, marketers, researchers, copywriters, and countless other stakeholders. We need the expertise of each to deliver effective websites and digital services. However, balancing those many voices can be challenging and being heard even tougher. Each stakeholder approaches projects with their unique perspective and personality. So it is unsurprising that this can lead to conflict and some voices being drowned out, resulting in simmering resentment. Yet the alternative is not particularly attractive either. Organizations that prioritize consensus do so at the risk of reducing progress to a snail's pace, nobody taking responsibility, and solutions being watered down to the point they please nobody. My Three Techniques to Working With Others So how do we run collaborative, cross-disciplinary digital projects without them either grinding to a halt from too many opinions or leading to conflict with one or two individuals dominating? Well, I have grown to favor three techniques: Establish clear ownership — Before I start any project these days, I try and get everybody to agree on who will have the ultimate decision. I seek to agree on one individual who makes the call when different voices disagree. You will find that people are reluctant to decide on this, but the alternative is some issues being almost impossible to resolve without painful and time-consuming debate. Have agreed upon objectives — I also seek to agree on a set of objectives and ensure these are prioritized. For example, is it more important to prioritize conversion over a positive brand perception? Should copy conforming to a style guide come before making a sale? Having these priorities establishes a pecking order in opinions, not based on seniority but the type of feedback and opinions being expressed. If in doubt, test — Probably the most important of the three, I have learned that the best way of resolving different perspectives is to test. That could be a survey, an AB test, unfacilitated usability testing, or whatever else gets the job done in a lightweight way that gets an answer fast. Don't over-engineer the testing; instead, seek to find a method that will get you an independent answer as quickly as possible. That last point also brings me to another aspect of working with others that, although challenging to hear, is true — just because you are the expert doesn't mean anybody will listen to you. Support Your Opinion With Evidence Despite all my years of experience and impressive portfolio of clients, I have learned that people will still not listen to me unless I can provide independent evidence. Now, whenever I express an opinion, I must present something to back up that statement. Either some piece of research I have done, some insights from analytics, or, if all else fails, an independent source who validates my opinion. In all honesty, this is often why I am hired. Internal digital experts are frustrated that stakeholders ignore them, so they turn to me as an independent outside source to validate their opinions. It is terrible that this is needed, but it does work. Trust me; I know how frustrating it can be to justify everything you say. You feel like you are wasting hours gathering the evidence you need. But the alternative is endless argument and debate that takes even longer. Working effectively with others is a skill like any other. It takes time to learn, and I still do not always get it right. However, delivering excellent digital services and sites is impossible without it. So my advice is to start practicing today, try things, observe what works and iterate!0 comments0
Podcast hosts
No host has claimed this podcast yet, if you are the host you can verify ownership by claiming this podcast
Keywords
© Boagworks Ltd
