Being a project manager (PM) can be a tough gig; when everything is going fine, you may, at times, be viewed with disdain: a mere “meeting scheduler” who collects status updates from the key stakeholders and SMEs, reporting them upwards. When everything isn’t going fine, they are in the cross-hairs of everyone: the key stakeholders, the SMEs and the higher-ups they report to.
Big data is a phrase that represents an extremely large information set that can be utilized, processed, and computationally analyzed in order to find patterns and material about a gathered set of data as a whole. At a simpler level, it is data that can provide answers to questions.
The concept of risk management—what it is and consists of—is something that is often misunderstood or misinterpreted. A big challenge many companies face is evolving the management of their risk and dealing with it properly as it changes. While risk itself is a recurring instance for most companies, the problem is not just dealing with different risks, but having a universal definition of what they are and also specifically having a risk identification plan.
Throughout the course of my career, I’ve collaborated with many, many SMEs. Sometimes I didn’t know I was with a SME, other times I knew exactly who and what they were. The best ones always had the same traits, the stuff that makes their expertise jump off the page, or at the very least, flow in a coherent manner through distinguishable disguise, ultimately ending up as valuable scribbles in my notebook.
Wherever you are in the platform evaluation process, narrowing your choices down and selecting a new solution is never easy. This guide helps balance out the pros and cons of what your needs really are as you evaluate your current system and prepare to make a final leap to a new GRC platform.
Much like fire and early man, the Excel-based RCM-to-Assurance Professional relationship has seemingly been in existence since the dawn of time (or at least the dawn of Excel). Thankfully there is a better way to manage this critical element of your assurance process. And you can do it without having to sacrifice what made the Excel-based approach so appealing in the first place—structured data, demonstration of key relationships, management of key attributes.
There are a lot of advantages to opening up your data—within reason. Team members who are both a key holder and a person trying to access sequestered data can find it to be a tricky proposition as to when to be an open model and when to remain closed.
Poor work results can almost always be avoided. If you’ve fallen into this trap before, not to worry. There is a way around the stressful feeling of not knowing what you’re doing, and a way to conquer poor time management, a bad habit that can take us down in a hurry.
A lot of fear comes from not being prepared, not having the correct support needed to fulfill and complete a job. The more it happens, the more FOMO creeps in and takes over, and that can become a truly destructive force in an office setting.
It’s funny how the mere mention of “contract review” causes tension in a room. In one corner, you have the people who are trying to execute a contract and get down to business. For them, the review and approval process can’t move swiftly enough. In the other corner, you have those who are responsible for going through contracts with a fine-toothed comb. They don’t want to be rushed in their work. It’s too important to get it right—and far too costly if things go wrong.
If your software provider is committed to keeping the product up to date and delivering new and valuable features, then your software implementation really should stand the test of time. But here’s the kicker: You have to take advantage of what’s available to you. Those new features from your vendor won’t do much good if you don’t incorporate them into your work. And when your team and processes evolve (as they always will), your software may need some fresh configuration to adapt to your changing needs.
As it turns out, doing things properly is almost always a good choice. Though reading instructions or planning ahead may slow you down in the beginning, you’re more likely to end up with a quality outcome. This is true when assembling furniture and when implementing new software—particularly if that software offers a great deal of flexibility. Taking a few days to plan your approach (rather than diving right in) can dramatically improve your chances of success.