A good admin panel speaks the language of your team.
Adding content, editing records and tracking work. Reasons to design the admin panel starting from actual daily tasks.
This article contains notes from SARBO's approach to digital product development.
Map daily tasks
When designing an administration panel, the starting point is not the number of menus. It is necessary to understand what records the team works with on a daily basis, what information it checks and what actions it repeats. The needs of the person adding content and the screen of the person tracking the order may differ.
It is useful for a first draft to write the user tasks in order: find record, change information, verify, save, see result. Screens or unnecessary areas that complicate these steps are easier to spot during development.
Fields represent actual content
It may seem easy at first to put every piece of information into one long text box. However, this approach is limited when information such as ranking, category or post status needs to be managed as separate fields.
For example, the title, description, content and social media links of a post have different functions. Keeping them in separate areas makes it easier to use the same content consistently across the blog page and social media links.
Make status changes visible
It should be possible to clearly manage whether a record is draft or active, on which page it appears and its order in the list. Giving feedback after the saving process and enabling the changed record to be accessed again are also part of this flow.
It is necessary to consider transaction authorizations together with the user's role. Not every user has to access the same areas or make the same changes. Scope of authority is determined according to project needs.
Consider use after delivery
We design the administration panel as a tool to be used not only for loading initial content, but as new records are added. As lists grow, the need to find, organize, and keep track of records may change.
In SARBO's content management and special software services, we evaluate the screens together with the workflow. The aim is to adapt the software to the actual way it works, rather than having the team work according to the internal logic of the software.
The quality of the panel appears in how clear the daily task is before how many features it has.
Is your panel following your team, or is your team following your panel?
There can be hundreds of features in an administration panel. But are the five actions your team takes every day clear? Add content, sort it, publish it, edit it and see the result. A good panel should start from real tasks. Domain names should be understandable. You should be able to find the change you saved. Build the flow of the software according to your team's work.