The Must Know Details and Updates on Custom App development

What Should Employees Be Able to Do on Their Phones Through Your Enterprise Intranet?


A supervisor checking the enterprise intranet ahead of an early shift may want to confirm whether any instructions have changed overnight. Meanwhile, another employee in the building may be looking for the latest expenses form. Both workers need information from the intranet without spending time browsing a department's main page. The design problem starts with the gap between what employees need at that moment and how the organisation has arranged its information. Resolve that mismatch before choosing which areas of mobile app development deserve funding.

Trace a single task from beginning to end


Imagine a maintenance worker receives a message saying a procedure has changed. They follow the notification to the intranet, read an overview and proceed to the actual procedure. At each step, ask what they need to know. Does the message identify the location affected by the change? Does the summary show when the change takes effect? Is it clear to the employee that the document displayed is the authorised version? If a step relies on knowing the author's name or recognising a file from a string of initials, the journey needs work.

Use a complete employee task as the basis for your design decisions. Put the reader in a real setting and have them start wherever they naturally would, such as an email, a saved shortcut or a search box. Watch for detours into team chats or messages to colleagues. An activity that looks simple during a demonstration may require multiple requests for assistance when someone attempts it without guidance.

Determine which features belong on the opening screen


An intranet home screen can only show a few things before people need to scroll. Give that space to actions and information that are useful in the employee's current setting. A warehouse team might need operational updates, forms and a staff directory. Someone managing several locations might require access to pending approvals alongside an option for changing sites. Employees who hold multiple roles should be able to identify their active role or location, especially before submitting a request.

Sort candidate features by frequency and by the cost of delay. Employees may consult a directory every day. A closure announcement for a site might seldom appear, yet it could be urgent. A quarterly newsletter can sit further down the page. At this point, clear priorities for content have a practical impact. Assign urgent updates to a defined audience and specify when they expire to keep the home screen relevant after the event. Use plain labels employees already recognise, especially for tasks with a similar name.

Make the content work before changing the delivery format


Responsive web design makes sense as an initial approach if staff primarily check notices, search for co-workers and open forms. Test the current intranet pages on a smaller display by performing those tasks. Check whether text can be enlarged, whether the menus make sense with a screen reader and whether a form keeps its entries after showing a validation message. Remember to examine the documents themselves. A neatly designed article page still sends readers into a difficult experience if the main instruction lives in a dense PDF with tiny columns.

The smallest fix may be to publish the instruction as a short web page and keep the full document available for reference. Make sure the page has a clear title, an identified owner and a scheduled review date. When employees search for “time off” but the official form says “annual leave”, make sure both phrases help them find it. It offers little benefit to transfer inadequately maintained information to a new application only to encounter the existing problems during pilot testing.

Decide which tasks warrant a custom intranet app


Evaluate different intranet solutions against the activities identified through testing. A mobile-friendly browser may meet the requirements of tasks that are primarily informational. Consider a custom intranet app when staff regularly perform tasks away from their desks and a particular mobile feature supports completion. For example, an employee may need to complete an inspection and attach a photograph. Staff working in areas with occasional connection interruptions may also need to save a draft.

Base each requirement on an outcome the team can directly examine. When defining inspection requirements, explain how the app should behave if an employee closes it during an attachment upload. The screen should show whether the report is saved as a draft or has reached its destination. If retrying is possible, test that the same report does not appear twice. These requirements incorporate dependable feedback on submissions part of the requirement from the start.

Plans for custom app development should account for ongoing ownership once the application has launched. Intranet mobile apps need someone to maintain their release process, respond when an operating system update affects a feature and support people who change devices. Assess the ongoing work required alongside the recurring errors or delays that the new experience could prevent. The investment becomes easier to support if improvements can be seen during an ordinary working week.

Test the SharePoint mobile intranet as an employee would


Where SharePoint is already in use, make the existing employee mobile experience your starting point. Pick a page and a document that people use regularly. Test opening each resource from an internal message, a search result and the main intranet page with accounts representing the relevant users. Trace the whole path through to the file, form or approval. Pay attention to how relocated content and requests for access are handled.

Some intranet applications collect information from resources that are the responsibility of separate departments. A page may be visible to everyone at a site while the form on that page is managed by a different department. During a pilot, check the transition from one system to another in collaboration with the teams managing both systems. If employees cannot send a request through their phones, establish where the task breaks down and who can address the problem. Give employees a clear route back to the task after an error.

Design for the phone people actually carry


A pilot built around a recent company handset can miss difficulties that appear on smaller or older devices. Use the mix of screen sizes and device arrangements that employees work with, including shared devices where those are in scope. Attempt to view a long notice using increased text size, enter information into a form with the keyboard open and continue a task after putting the device away. Someone completing a task on a short break might experience multiple interruptions, even when the same action took only thirty seconds in a calm meeting room.

Shared devices deserve their own test. Examine what happens as one shift passes the handset to the following shift. Verify what becomes visible to the incoming employee when they access the intranet and whether the outgoing worker can still Custom App development retrieve unfinished tasks in accordance with organisational access rules. If staff use personal devices, agree what information can appear in a preview or be kept on the device before choosing delivery features. These tests should reflect how devices change hands at work.

Use birthday email automation to set rules for everyday messages


Birthday email automation provides a manageable and practical opportunity to establish rules for staff communications. Private greetings, announcements to teams and public intranet posts each reach a different audience. Agree what kind of celebration employees can opt to receive or share, which information is necessary for the template and how records or communication preferences can be changed. Since a greeting usually needs only a small amount of personal information, determine the storage location and ownership of the relevant record.

Evaluate timing and audience rules using realistic workplace examples. Where employees are based in different time zones, establish which local date controls when the message is sent. If an employee has opted out, include that case in testing alongside a record with missing details and one with a recently changed preferred name. Establish what should happen to a scheduled message that does not send successfully and is subsequently picked up. Similar attention is useful when establishing reminders for expiring policies and everyday internal deadlines, as a message that arrives too late may no longer serve a purpose.

Judge the pilot by tasks people can now finish


Include staff who routinely perform the work as well as a small number of recent recruits. Create realistic workplace situations and have employees work through them on their everyday devices. Ask a supervisor to check whether a revised instruction applies to the next shift and an employee to find out whether a form they submitted went through. Examine where employees encounter difficulties, how they recover and whether they can describe what happened independently of the person conducting the pilot.

Document the causes of task failure as well as rates of successful completion. When staff consistently choose an incorrect form, examine the naming conventions and search results. When employees leave a request unfinished after losing connectivity, review how the system stores and displays their progress. When staff complete an activity yet contact co-workers to clarify the next step, examine the guidance provided on the confirmation screen. Each finding should lead to a change someone can own and a task the team can repeat after the change.

Questions to consider when organising a mobile intranet pilot


Before introducing employees to the revised intranet, decide how findings will be communicated and how existing shortcuts will be managed.

Should pilot results be reported by individual employee?


For usability testing, group results by task, role or working conditions where the group is large enough to protect participants' privacy. This generally provides the project team with sufficient information to examine issues. Tell participants what will be recorded and ask for their permission before capturing a screen that could show personal or operational information.

What should happen to an existing shortcut when a page moves?


When platform capabilities permit, preserve the functionality of the original address so users reach the page in its new location. If that is impractical, leave a short notice at the old location for a defined period and have the content owner update commonly used internal references. Check the existing shortcut on a mobile device, including a shortcut retained by someone participating in the pilot.

Conclusion


A mobile intranet provides genuine value when staff can locate up-to-date information or complete an activity within the time available to them. Start by examining a process that frequently requires staff to seek assistance from co-workers. Improve the information employees must read, the steps they need to follow and the way completion is communicated. The outcomes provide a practical foundation for choosing where further development is worthwhile and where improved ownership or simpler content would be more appropriate.

Leave a Reply

Your email address will not be published. Required fields are marked *