<< BACK TO KLOUDGEM.COM HOME

Tuesday, November 26, 2024

KloudGem picks up where the job of your IT Help Desk ends

KloudGem picks up where the job of your IT Help Desk ends:   - we consult with your users or teams to smooth out or   reimagine their workflows within the Google Workspace ecosystem,   and   - as necessary also work with them and your IT Team to provide   custom-tailored training and company-specific guidance,   so that your IT Team and your company can reap the intended cost- and productivity benefits of working in Google Workspace.

KloudGem picks up where the job of your IT Help Desk ends: 

💎 we consult with your users or teams to smooth out or reimagine their workflows within the Google Workspace ecosystem,

AND 

💎 as necessary also work with them and your IT Team to provide custom-tailored training and company-specific guidance, 

so that your IT Team and your company can reap the intended cost- and productivity benefits of working in Google Workspace.


Thursday, November 21, 2024

Mistake 6: IT KPIs - 6 Costly Mistakes When Rolling Out Google Workspace — and How to Avoid Them

Mistake:  IT KPIs: Traditional IT Help Desk Key Performance Indicators (KPIs) create, rather than solve problems:    Problem:  No matter how similar workflow consultations might be to IT Help Desk tickets, measuring them by using the traditional KPIs of how fast a ticket is closed will create the wrong perception in users that IT does not cater to users' needs. This will lead to dissatisfaction with IT.    How to avoid:  Workflow and process consultations can be measured by such questions as:   Do the users feel that they have an ally to help them find the right workflows?   How easy is it to access the consultations?   Do the consultants immerse themselves in the work and think with the users/teams to work through options?   Do they advocate for closure of IT tool gaps?

When it comes to measuring your IT Help Desk's effectiveness, we believe that we need to look at it 2 ways:

🛠️ Fixing issues

⚙️ Thinking through workflows

Traditionally, metrics only look at the first.

For the former, the more traditional metrics work well: how fast was the person able to solve a technical issue, how many times a user had to contact the Help Desk.

For the latter, a simple fix-it-quickly approach is not going to work: there, you need your consultant to be able to put themselves in the user's shoes, really understand what they are trying to accomplish, and be their problem-solving ally. This requires a very different type of skill set. It requires an operations expert. And it cannot be measured with the traditional Help Desk KPIs.


Wednesday, November 20, 2024

Mistake 5: MICROSOFT AND GOOGLE TOOLS - 6 Costly Mistakes When Rolling Out Google Workspace — and How to Avoid Them

Mistake:  Microsoft and Google Tools: Failing to provide guidance on how to make Microsoft and Google tools work together    Problem:  If your organization uses Microsoft files within your Google environment, eventually, you will hear about user dissatisfaction with regards to any of the below or a combination thereof:  Microsoft file formatting getting corrupted when opened by Google tools.  Google tools not having necessary formatting capabilities.  Some team members using Microsoft, others using Google files, creating inconsistency and confusion.      How to avoid:  These issues can be mitigated by:   Providing consultative guidance, and   When necessary, training on best practices for using Google Drive via Chrome vs. Google Drive for Desktop;   Bringing guided discussion to the team levels to establish team collaboration ground rules.

Working in Google files speeds up collaborations, but IT departments need to be keenly aware of any Microsoft office/file usage needs across your organization. Why? Because unbeknownst to you, there could be segments in the organization who need them for reasons outside of their or your control, perhaps because of file format requirements from outside agencies, working with outside partners, legacy files, etc. 


When this needs arises, it is advisable to deeply understand the why and the constraints. If it's just a preference, then sure, you can encourage Google tool use, but beyond that, if there is a specific non-negotiable need (as mentioned above), they might be experiencing file corruption issues when they use Google Drive's native compatibility feature that translates Microsoft files into the Google format. If this will inevitably cause dissatisfaction with the IT tools and IT's support, as well as #ITcost for your company in storage. Because, likely, people will start uploading and downloading Microsoft files, perhaps even emailing them instead of sharing, creating multiples of the same, resulting in increased storage costs and slowdown in productivity due to version control. And when the dissatisfied voices get louder about Google tools, it's hard to mitigate the damage.


So why not provide solutions instead? Consultations can ensure that those who need it, have Microsoft Office, and can use it in conjunction with Google Drive: raise awareness about how to store files in Google Drive, and share best practices for when to use Google Drive via Chrome vs. Google Drive for Desktop for natively editing Microsoft files.


Be or provide consultative guidance to your users so they can comply with IT's requirements and still get their work done.

Tuesday, November 19, 2024

Mistake 4: STORAGE - 6 Costly Mistakes When Rolling Out Google Workspace — and How to Avoid Them

Mistake:  Storage: Expecting users to define and establish document management best practices    Problem:  Duplication of files ⇒ confusion on the user side + significantly increased storage costs on the IT side, both in Gmail and in Google Drive.  File ownership and access issues when people leave the company or move between teams.  Confusion about where to look for files. And user confusion ⇒ increased IT tickets.    How to avoid:  Seek cross-functional alignment on document management strategy, with input from IT, Legal, Operations, and User teams.  Communication and training on guidance, strategy, and best practices by an expert who can tailor the content.  Providing opportunities for workflow consultations to users and teams.

One of the reasons you moved your company to GoogleWorkspace is to save on storage: by teams accessing the same file, instead of keeping various versions, everyone wins: smoother and faster collaboration for your users and cost savings for the company. However, expecting your users to define and establish document management best practices for themselves and their teams will undermine your digital transformation efforts. 


Without guidance, users will interact with Google files the way they used to with offline files, and this will only lead to duplication of content and version control issues -- as well as significantly increased storage costs on the IT side (both in Gmail and in Google Drive). Added to this, there are bound to be file ownership and access issues when people leave the company or move between teams. 


Without a shared strategy, there will be confusion about where to look for files. And user confusion always ends up in increased IT tickets.


How can you avoid it? Seek cross-functional alignment on document management strategy, with input from IT, Legal, Operations, and User teams. Then communicate the strategy to your user teams, and train your users on the guidance, strategy, and best practices. Get help from an expert who can tailor the content. 


Provide opportunities for your users and their teams to have access to workflow consultations with a Google Workspace expert. Your people will thank you for it, and you can avoid unwelcome cost increase.

Tuesday, October 8, 2024

A consultative addition to IT Support

Person resting his head on his laptop over his desk, with a coffee mug on the side.


I haven't yet come across an organization where the employees love their IT Departments. 💻


But this post is not about criticizing IT; the issue is that expectations are misaligned: 


Your IT Department is prepared to help with any technical issue around the hardware or software that they support.


On the other hand, users don't always come with technical issues. Sometimes their issues are more about day-to-day operations, processes, workflows, or best practices for working together as a team.


Specifically, you might hear that they need help with: 

🗃️ File management: optimal organizing of own vs. team files, or reducing file versioning issues in Google Drive 

📧 Email management: reducing email overload in Gmail with some sorting automation 

🤝 Team effectiveness: working and communicating effectively within their team using the Google tools.


And it is not IT's job to remedy this.


However, your IT Department can absolutely help solve the problem: KloudGem can work with users on problems that are not strictly IT Support in the Google Workspace world; we add a consultative approach. We can round out and add value for your users' experience with IT Support.


What other non-IT questions do you get from your users who work in Google Workspace?

Monday, September 30, 2024

Floating audience in Google Meet

YouTube thumbnail: Google Meet: Floating audience


From now on, it's going to be so much easier to see your meeting participants at the same time as looking at another tab or sharing your screen in Google Meet.


Finally! The Google Meet feature I've been eagerly waiting for is here!


It always confused my clients when they couldn't see me while they switched to another tab or were sharing their screens. 


Well, technically, you could make it happen, but you had to take an extra step to open what's called Picture-in-picture. And it took time away from our topic to get that floating camera feeds set up just right.


But no more Picture-in-picture acrobatics! Now, you can effortlessly keep others in-view while you move to another tab as you present. 


💎 Watch the video to see how the Automatic picture-in-picture works.



Need help with Google Workspace? Schedule a Discovery Session:

https://www.kloudgem.com/contact-us 


KloudGem tips: 

https://www.kloudgem.com/follow-resources/newsletter 


Tuesday, September 24, 2024

Mistake 3: FEEDBACK - 6 Costly Mistakes When Rolling Out Google Workspace — and How to Avoid Them

Mistake: Feedback: Using an “as needed,” rather than a continuous feedback process to improve the implementation  Problem: Dissatisfaction with IT and the tools you provide,  Which may undermine your efforts to transition the company to Google Workspace, and  It will be costly to migrate back to your original ecosystem.  How to avoid: Listen to any concerns, confusion, or dissatisfaction from users, and provide an avenue to channel that feedback to you on a continuous basis.  Then perform gap analyses on the feedback.  As a result of which,   either look for software solutions, or  provide users with access to expert workflow consultations.

We all know that user feedback is important, but it should not be a 1x or 2x a year survey. As an IT Team, you want to make sure that you have set up channels through which you can be in continuous communication with your users about the tools that are deployed to your company – and not just for Google tools. I see that in many places, IT is perceived to be this department that imposes rules about how to work and what to work with. I believe that it is in IT's power to change that view. IT needs to be and can be a trusted partner in facilitating work for all employees. Unaddressed dissatisfaction with the tools and/or IT may undermine all your technical efforts of your Google Workspace rollout. When the grumbling starts about people not being able to use the tools effectively, it is not just their problem, it is your problem as IT. If the tools are perceived to be ineffective for day-to-day work, it can be costly, not only because the company as a whole is not as productive as it could be, but you could be forced to migrate back to your old systems despite you as IT Team knowing full well that Google Workspace is better for collaboration and productivity.


So what can you do? Open up channels to listen to concerns, not just in the form of a written feedback survey, but also allow for users to reach out in person to someone. And really listen. Once you get the feedback, record it, aggregate it, and assess it: you will likely find that an issue is either one that consultations and training or some easy tweaks can fix, or you'll need to partner with the users and look for software solutions for them or build them. Aggregating the information coming from your users, and aggregating and assessing the data coming in through different channels will be a key element. And don't forget to circle back to users so they know you heard them and are working with them.