Posted in

How to create a user – friendly interface for indoor digital signage management?

If you’ve ever stared at a glitchy, half-updated restaurant menu board that’s two days out of date, or a gym’s workout schedule that still promotes a class that got canceled last week, you’ve run into the frustration of bad indoor digital signage management. Back when I first launched my indoor digital signage company, I’ll admit I fell into the same trap many new tech providers do: I thought the flashiest screen, the most fancy graphics, and a long list of “advanced features” would win clients. What I didn’t get at first was that 90% of the pain points my customers were complaining about weren’t about the hardware—they were about how hard it was to actually use the software to manage the screens. A school’s admin team couldn’t figure out how to swap a lunch menu in five minutes between periods; a retail store’s part-time associate had no clue how to fix a broken ad that wouldn’t stop playing. That’s when I shifted my entire product focus to building interfaces designed for real people, not just tech experts. If you’re someone who’s been stuck wrestling with clunky signage management tools, or if you’re a business looking to invest in your own indoor digital signage, this post is for you. Today I’m breaking down the lessons we learned, the mistakes we fixed, and the actual, actionable steps to create a user-friendly interface that anyone can use—no tech degree required. Indoor Digital Signage

First, let’s start with the most basic rule that took us years to internalize: know who your actual users are, not just who signs the check. When we first surveyed our early customers, we made a huge mistake of only talking to the CFO or operations director who signed our contract. They told us they wanted “enterprise-grade security” and “scalable for 1000 screens”—things that matter for long-term budgeting, but they never used the software day-to-day. The real users were far different: the part-time café manager who only needed to swap a menu in 10 minutes, the high school’s media coordinator who juggles 12 other school tasks, the retail shift lead who gets 15 minutes between closing and opening to update weekend sales. These people don’t care about API integrations or custom API endpoints—they care about “can I click something and get this done fast.” For example, when we redesigned our dashboard a couple years back, we sat in on three café manager training sessions and watched one of them spend 20 minutes trying to find where to upload a new menu. Turns out, we had hidden the “content upload” button under three layers of menus, tucked away under “Advanced Settings” because we thought it “didn’t need to be front and center.” We moved it to the top of the main dashboard, right next to “Schedule Post,” and cut their average task time from 20 minutes to 90 seconds. That’s not a small win. Another key part of this is building user personas for every role that touches the interface. We created personas like “Mia, 28, part-time café manager, works 30 hours a week, no formal tech training beyond basic Instagram,” and “James, 45, high school media coordinator, manages 10 other projects, only uses this tool during school hours, has to answer to admin if something breaks.” Every single change we made to the interface got run past these personas first. If a new feature or button would only make sense to a tech-focused user, we didn’t add it to the main dashboard—we tucked it into an “Advanced Tools” section that’s hidden unless you explicitly enable it for that role. That’s how you make an interface that works for everyone, not just the people in the boardroom.

Next, keep complexity out of the core workflow. When we looked at why so many of our early clients churned, one of the top reasons was “the management tool is too complicated for our team to use.” We’d built a tool that could do everything from streaming live TV to creating custom animated ads, but when you log in, you’re flooded with 20 different icons, 15 different menus, and a pop-up every 10 minutes asking if you want to upgrade to a “Pro Plan.” It was like walking into a grocery store where every aisle is labeled with a random code, and nothing is where you’d expect it. The solution we landed on was what’s called “single-task prioritization”: each core user’s main job should take no more than three clicks to complete. Let’s take the example of updating a piece of content, the most common task anyone will do. Before the redesign, the steps were: log in → click “Content” → click “Create New” → choose content type → upload file → adjust settings → assign to screens → set time and date → save. That’s 8 steps, and it required adjusting 5 different settings most users didn’t understand. Now, we reworked that to: log in → click “Update Content” (right on the dashboard) → select the piece you want to swap → upload your new file → drag and drop to select which screens to show it on → set start and end time → save. That’s 5 steps, and we removed all the unnecessary settings that don’t matter for core use—like resolution presets, which default to the best option for the client’s screens automatically. We also added a “Quick Swap” feature for users who need to update something even faster: if you’re in a rush, you can just log in, click “Swap Menu” from the dashboard, and it pulls up your last 10 menus to pick from, no extra steps. Another thing we did was get rid of all the distractions. The old dashboard had a scrolling news feed, upgrade banners, and analytics widgets that no one actually looked at. We replaced that with a clean, static view that only shows what you need right now: a list of your screens and their statuses (green means working, yellow has a small issue, red is offline), the last five updates you made, and a big button for the most common task. For power users, the advanced tools are still there if you need them, but you have to actively go look for them—so the average user never has to see them. That’s the balance we were missing earlier: give experts everything they need, but hide it so it doesn’t confuse the people who just need to do a simple job.

Then, make feedback and error messages actually useful, not confusing. I can’t tell you how many times I’ve gotten an error message on a tech tool that said “Error Code 404: Content Not Found” and had no idea what to do next. That’s a huge problem for digital signage management, because if a screen is broken, you need to fix it fast, not waste 10 minutes searching for what the error means. Early on, our error messages were exactly that generic code, and our support team was getting 100 tickets a week from users who couldn’t figure out why their ad wouldn’t play. We completely rewrote every error message we had. Now, if a screen is offline, it doesn’t say “Screen Status: Offline” and leave it at that—it says “Screen #3 (Café Front Door) is offline. Possible fixes: 1. Check that the screen’s power cord is plugged in; 2. Reboot the screen by holding the top button for 10 seconds; 3. Call support if these steps don’t work.” We even added a one-click “Troubleshoot” button next to the error that pulls up a step-by-step video tutorial for the most common fix. For content errors, if a user uploads a PDF that’s the wrong size for their screen, the message doesn’t say “Resolution Mismatch”—it says “Your menu PDF is 1920×1080, but your café screen is 1280×720. Would you like us to automatically resize it to fit, or would you like to adjust it manually?” That takes the guesswork out of fixing issues, which cuts down on support tickets by over 70% and makes users feel like the tool is working for them, not against them. We also added a simple feedback button on every single page of the interface. It’s a little thumbs up/thumbs down, with a text box to leave a comment, and it only takes two seconds to use. Every day, I get a digest of the most common feedback, and we’ve used it to fix everything from buttons that were too small (making it hard for users on phones to navigate the tool) to a typo in a menu label that confused a whole cohort of café managers. Feedback shouldn’t be a quarterly survey that no one fills out—it should be built right into the interface, so it’s easy for users to tell you exactly what’s wrong, right when they’re using it.

Another big one: design for mobile, because most users aren’t at a desk when they need to update a screen. Back when we first launched our signage management tool, it was only built for desktop. A retail shift lead would have to leave the store, go home, log in on their laptop, and update a sale ad during their break. That’s a huge hassle, and it meant they sometimes skipped updating the screen, leading to out-of-date content. So we built a fully responsive mobile interface that works on any smartphone, and optimized it for one-handed use—since most people are using their phone while standing in the store or school hallway. The mobile version keeps all the core features: swapping content, checking screen status, setting schedules—all in one tap, no zooming or pinching required. For example, the mobile dashboard has a big, tapable list of screens, and tapping on a screen pulls up its status and the option to update content or troubleshoot. We tested this with a group of retail shift leads, and they told us they now update sales in less than a minute while they’re walking past the screen on their way to the back office. We even added push notifications, so if a screen goes offline, they get a text alert on their phone, not just an email that might sit in their inbox for hours. That small change alone made a huge difference in how often content is kept up to date, because users don’t have to be tied to a desk to do their job. It might seem obvious, but so many digital signage tools are still desktop-only, and that’s a major barrier for users who are on the go.

Finally, test, test, test—with real users, not just your team. I can’t tell you how many times our in-house designers would build a new feature, show it to the team, and everyone would say “That looks great!” only to have a real user try it and get completely confused. The best lesson we learned was that you don’t need a big user research budget to test your interface—you just need to invite a handful of your actual customers to sit down and use the tool, while you watch. A couple years ago, we tested a new way to assign content to screens, and our internal team thought the drag-and-drop feature was intuitive. When we had a group of café managers test it, one of them spent 10 minutes trying to drag a menu to a screen and couldn’t figure out why it wasn’t working. Turns out, we’d hidden the drag zone in a tiny corner of the screen, and it wasn’t big enough to tap with a finger, especially on a mobile device. We expanded the drag zone to cover the entire content card, and suddenly it worked for everyone. We also run ongoing beta tests with new features before we roll them out to all clients. Any new tool or update gets sent to 10-15 random customers who fit our core personas, and we ask them to complete three common tasks using the new feature, then give us feedback. If more than half of them get stuck on a single step, we go back and fix it before anyone else sees it. That’s how we avoid rolling out messy, half-baked features that confuse users. We also schedule quarterly check-ins with our core users, just to ask what’s working and what’s not. Sometimes it’s a small thing, like making the text on the buttons bigger for users with bad eyesight, or adding a way to save favorite content so they don’t have to re-upload the same menu every week. These small, user-centered changes add up to an interface that actually works, because it’s built around how real people use it, not what the engineering team thinks is cool.

At the end of the day, a great digital signage management interface isn’t about how many features it has or how sleek it looks. It’s about making it easy for the person using it every day to do their job well, without frustration. When we shifted our focus from building a tech product to building a tool for real people, we didn’t just keep our existing customers—we grew, because clients would refer us to other businesses saying “I’ve used so many of these tools, and this one actually works.” If you’re an indoor digital signage provider, remember that your product isn’t just the screens you install—it’s the software that lets clients actually use those screens. If you’re a business looking to invest in signage, don’t just look at the hardware specs—ask to test the management interface yourself, using the same tasks you’ll actually need to do. If you follow these steps, you’ll build an interface that reduces stress for your users, cuts down on your support tickets, and makes indoor digital signage actually do what it’s supposed to: communicate clearly with your audience, without the hassle.

If you’re looking to partner with a provider that builds indoor digital signage tools designed for real-world users, reach out to our team to discuss your needs and see how we can help your business succeed.

Bus Screen References
Nielsen Norman Group. (2020). User-Centered Design 101. Nielsen Norman Group.
Google Design. (2021). Responsive Design Guidelines. Google LLC.
Software Advice. (2022). 2023 Digital Signage Software Trends and User Pain Points. G2 Crowd.


Shenzhen Oshika Technology Co., Ltd.
With abundant experience, we are one of the most professional indoor digital signage suppliers in China. We warmly welcome you to buy high quality indoor digital signage made in China here and get quotation from our factory. For price consultation, contact us.
Address: 301, No.6-18, Xinhe Avenue, Xinqiao Community, Xinqiao Street, Shenzhen, Guangdong, China
E-mail: ludy@sz-osk.com
WebSite: https://www.sz-osk.com/