"You can use social media effectively in conducting UX research for your digital products or services." 

When you read this sentence, the first thing that pops up may be a classic LinkedIn question: "Which design is beautiful?" please bear with me; I have something better than that...
Let's make a classic start. I am in charge of the UI/UX for a Vodafone app that allows users to manage all devices connected to their routers. The goal of the task was to improve the device list page because we gathered negative feedback from our customers who wanted to find their newly added device/s in their network. After the initial interview with one customer who had that problem, it turned out that some of the wireless devices' fingerprints either were empty or did not match the device type, i.e., "Unknown-a2:a5:96:7e:c8:7f"
"Demystifying a possible solution is a consecutive communication progress with the right stakeholders."
I prefer concise articles, so I will list progress as bullet points and discuss social media research.
1. Define the problem
2. Brainstorming sessions with the team
3. Analysing the API

4. Surveying to clarify the information prioritisation based on users -> LinkedIn groups
Almost all of us use a router to connect to the internet and add some devices to our network. How many of us tried to find a newly added device in his/her network manager? Not many except the power users. That's why running a survey in Liknedin made sense at that point since there are a lot of target users.
To begin with, I analyzed the API and found that it returned eight attributes of device information. As a user, what would be the most beneficial information that helps you easily distinguish a device with an unknown name? Let's see what LinkedIn members choose. I split up the answers and posted two groups on Linkedin (as you may know, LinkedIn does not allow adding more than four options for polls)

a screenshot of a small piece of logic flow

Social media helped me to have a quick overview regarding prioritisation. 
Now, let's jump on the most crucial step: creating the logic flow together with devs because it is evident that we could not show all eight pieces of information per device in the list; otherwise, we would cause information overload.
As I recall, we had at least three meetings where we put our heads together to discuss the flow. We had many insightful conversations on FigJam as well. Our collaboration and hard work led us to have a reasonable flow.
Let's move forward to the exciting stage of visual design. However, we encountered a minor bump in the road as we currently don't have any credit available for testing. I didn't let this setback discourage us. Instead, let's find creative ways to overcome this challenge and move closer towards our goal. 
GUERILLA TESTING 😎 🚀 
"If you want the right information, ask it correctly." 
We have suffered enough from the "Which UI is beautiful?" question, right? Therefore I put some context to the question and posted two groups on Linkedin.
Left: current solution. Right: new suggestion. 
The new design got the most appreciation. Besides voting, I got beneficial feedback and implemented it in my design.
After thoroughly presenting the entire process to the team, we confidently decided to move forward with the new version without delay in testing it with our clients.
Our device listing section has been receiving positive feedback from the market for six months, with no negative comments.🤞🎉
Back to Top