1 credit
With Apple set to release public betas of macOS 13 “Ventura” and iOS/iPadOS 16 in July, it’s inevitable that some pro users will want to get a quick taste of what’s to come. The typical IT reaction is to try to prevent users from trying out beta software, but that might not be the most beneficial way to deal with what’s to come.
In fact, IT managers can actually make these betas — and enthusiastic early adopters — work in their favor.
Developer betas of new operating systems have been released after Apple’s Worldwide Developers Conference (WWDC) opening speech. The public betas that follow can be useful for a manufacturer like Apple in terms of speeding up feedback and releasing bug fixes during the development process. They can also be exciting for users who want to try new features in an upcoming operating system before everyone else gets their hands on them. (The final version of all these operating systems will not be available until this fall.)
But they pose obvious challenges for IT, especially if beta testers are installing pre-release software on their primary devices they use for work. Bugs, issues with existing apps, and confusion over new or changed features are often part of the beta testing experience. Thus, users who install unsupported software on business devices can result in support calls and employee downtime if they cannot access basic tools.
Remind beta testers that they are installing pre-release software
Keep in mind that since mobile operating systems have shifted much of the upgrade process to users, it’s likely that IT managers won’t be able to stop everyone, especially if they install on a device they own.
The best advice here is to inform users who wish to sign up as beta testers that they must do so using a secondary device instead of the one they rely on for critical work and personal tasks.
It’s essential to craft a nuanced message, which truly describes the challenges they may face in a friendly and consultative way, but which does not alienate those who wish to be part of a beta program.
Explain that, yes, they will be able to use the new features before anyone else, but also that there may be challenges that could impact the ability to do their job if they install them on their primary device. And be sure to note the potential impact on the personal tasks they rely on this device to accomplish.
Credit: Apple Turn beta testers into an advantage
Like most early adopters, many of these beta testers will likely be somewhat tech-savvy, though their savvy may vary. As a result, most organizations will encounter the public beta at some point this summer. Ideally, it will be on a secondary device, although some people will probably install it on their primary device.
Users can actually recruit these users as helpful allies.
One of the challenges in today’s landscape is that IT departments are generally expected to be ready for new technologies to walk through the door the day they are officially launched. This means users have a limited window of opportunity to check them out now, test key enterprise and third-party apps with them, and build a knowledge base of issues that support teams may encounter.
All of this is a tall order to achieve in a matter of months with existing staff and all of this requires beta testing. If IT managers recruit beta users, they can perform much of this testing for them. They can see which apps have issues, which workflows need to be changed, and report any general support issues. This gives IT greater readiness, both in terms of updating applications and in terms of developing materials and resources for users.
The approach requires a bit of a culture shift for many organizations. IT staff should develop a close working relationship with these users and should actively seek their input, advice and feedback.
On the other hand, it makes it easier to be prepared for new technologies and allows the IT department to be better prepared when these technologies are officially released. It also promotes a closer relationship between IT and workers who want to use the latest technologies. In the process, it can even help users manage ghost IT operations going on in the organization – or at least help identify them – because the people looking to try out a beta are likely the same people who would actively install tools or services. without bothering to inform the IT department.
Of course, that doesn’t mean everyone should be allowed to try out beta software — and IT managers shouldn’t just ignore the testers they recruit. Nor does it mean that IT staff should ignore the betas themselves (ideally they will use developer betas rather than public betas).
But embracing Apple’s upcoming public betas could give IT a head start on what’s to come this fall – if they can develop a trusting working relationship between everyone involved.
Key words Apple
#Apples #Upcoming #Public #Betas #Work #Computing