i remember a gift i bought my parents once – a motorized corkscrew that promised to make opening a bottle of chardonnay a cinch. when visiting once, i noticed it was tucked away at the back of a cupboard. i found out later it was used only twice. to my dismay, the pricey device had some fatal flaws – the button was too hard to press and hold. but the clincher was that it took about 65 seconds to open a bottle, as compared to 5 seconds with regular corkscrew.
gadgets are often throwaway, but in my experience this phenomenon of poor design happens in the schedule software world just as easily.
integrating your financial system with primavera p6 seems to make a lot of business sense. at this year’s collaborate14 oracle user’s conference held mid-april in las vegas, there were some great sessions on integrating financials with oracle primavera p6 – and some great success stories too.
it does seem to make good sense.
since p6 is not a very strong project cost management tool, just pull in cost information to p6 from your cost system. the ultimate goal is unified cost and schedule in 1 system – a holistic view in one place that is automated, no tedious spreadsheets or cutting and pasting.
but it’s been my experience that if you’re not careful, you may be building a system that your end-users will want to toss into a dark cupboard somewhere, hoping you’ll forget about the whole thing next time you drop in for a visit.
for those that are considering or are already in the process of integrating oracle primavera p6 with a financial system, here are 4 reasons your end-users may not want to curl up and hide, rather than use the new system.
1 – it’s too complicated
exerpt from user training manual:
“first start in sap, then set your project id, request an admin to sync the data. then goto primavera p6, set your wbs, but don’t use any numeric characters – it won’t sync, then request a sync from an admin. then back in sap, create your work orders, but don’t set dates. set dates in primavera p6…….”
if you need a phd and the patience of a monk to use the system, then it’s too complicated.
users will abandon any system that is too taxing to figure out and too hard to use – especially integrated systems where data flows from one system to another in a way that may not be obvious for the user.
often in integrated primavera p6 cost and schedule systems, users will have to perform specific tasks in each system – like adding and editing wbs only in sap, for example, even though natively you can edit wbs in primavera p6. the added workflow rules an integration typically brings may just baffle your users.
2 – they don’t have time
are you busy at work? understatement of the year?
how would you feel if your boss insisted that you learn how to code in java effective immediately and that java development would be a regular part of your daily duties? oh yeah, you’ll start coding immediately after some training but we’ll need to see your code quickly so it can rollup into the executive dashboard.
now assuming you’re not a coder, but a project scheduler working on a bunch of intense projects, your new coding responsibilities would likely have you sweating.
you would probably be asking:
how can i possibly find time to learn something so complex while still getting my regular work (aka your job) done?
your schedulers might ask the same question when you rollout an integrated primavera p6 system. will they have the time to learn it? will they be given time to master it?
3 – they don’t care about integrating schedule and cost
do your users have buy-in for your proposed integration of primavera p6?
do they have a cause they can rally behind? something that will benefit them.
a lot of companies position an integrated primavera p6 cost and schedule system as benefiting primarily the managers and executives. it true, they will be able to get unparalleled unified reporting, have one central source for project data, and as a result be more strategic in managing the business. these factors are definitely important, but are heavily one-sided.
what’s in it for the users?
your users are the force behind the flow of project data that drives the business.
most users don’t care about integrating primavera p6 and your financial system. they probably liked the way things were – the systems worked fine in their eyes before they were integrated.
if your users don’t have some motivating benefits for changing their behaviours, your integration rollout will likely be met with resistance. and you will have users who resent being forced to use a system that requires a lot more work to function.
4 – you tried to teach them everything in one training course
the 3 or 5-day introduction to primavera p6 training course has become a standard around the world.
but in the case of a complex primavera p6 integration, you don’t want to overwhelm your users by delivering a whopping amount of content in a short period of time – as cost-effective as it might seem.
we all learn in chunks. we take a process that we’ve just been taught and we try it a few times and then integrate it into our own daily routine.
without access to continuous learning tools that provide users with a curriculum for learning over time, your users won’t be able to remember and integrate all that they’ve learned into new behaviours. and then they won’t change their behaviours and your integrated primavera p6 system won’t get much use.
