The Benefits of Project Management Software

By Lauren Grabiak, Workbook

 

What Can Project Management Software Do For You?
They key to success and organization within a company is the ease of finding the tools you need in a single area. Project Management Software does just this for you. Regardless of the size of your company, this software type can be molded to fit you in order to ensure the highest productivity of your business. Here are just a few examples of what Project Management software can do:

Communication
Project Management Software allows you to comment on tasks, jobs or messages on a tab in order to keep all of your messages in one, singular place. Files can be sent and replies can be made in a timely manner. In addition, communication can occur with clients over this channel in order to track the progress of projects and implementations. You will no longer have to flip between messages, emails, etc. to communicate with people.

Scheduling
Not sure of a deadline? Managers of certain projects and jobs are able to add deadline dates to ensure work is completed before an allotted date. All deadlines can be seen in lists for regarding jobs to keep you organized and working efficiently. You can even view your tasks in terms of time schedules to help better allot your agenda.

Collaboration
Different tasks require different people working on them, but Project Management Software allows the bigger picture to be seen as well. Employees with different tasks can see how other tasks are being handled in order to work together for the job as a whole and see the status of how far it’s coming along. Tasks may simply be redelegated to other employees as well to make the transfer of work even easier!

Time Entries
This type of software makes it possible for you to log hours for each job after each section is finished. Furthermore, it allows you, as well as managers, to see how much time you’ve spent on each task, so you can keep up work with other tasks as well. Every task or job requires different time allotments, and this feature makes it easy to see that visually.

There is so much more that Project Management Software can do for you than these 4 components can say in words. See for yourself today.

 
Workbook+project+&+resourcing+view.png
 

20 Years. An agency systems perspective.

Chris Lever, Founder, Agency DNA

My first UK marcoms role was in 1995 as agency FD of Bernard Hodes, an Omnicom/DAS group company. Obliged to conform to the rigour by which DAS managed its portfolio and deliver rapid improvement in their two key pertinent drivers, profit margin and the working capital ratio, I was aghast at the way DDS, the group imposed agency media booking/billing, job management and accounting system, made getting these metrics a major exercise. A single minded Kiwi Financial Controller who I’d hired to assist me had words I couldn’t even begin to pronounce for a system which offered not only opportunity for one-sided entry, but produced a balance sheet by downloading disparate ledgers and combining them in Excel.

chris.jpg

Fast forward 20 years, DDS rebranded as Media Ocean, rebuilt its database, and yet seems it still can’t handle supplier invoices with more than six characters, or allow a major network create a new field to hold the PO references of Google and Facebook, who quite rightly have their own booking systems. If a network with two billion pounds passing through its pay-as-you-go ledgers doesn’t get what it wants, what hope might a smaller agency have? Excel is a strong supplement.

Step back fifteen years and I’m on a team with other senior players from BMB&B, Leo Burnett and  BBH collectively giving up weeks of our lives to work with Maconomy, guiding them on the development of their agency solution on top of what was admittedly a complex, yet robust financial system.

Youthful and optimistic this was heralding a golden age where a Scandinavian vendor understood that agency complexity is a state of mind, we then waited for the release of a system that would look as good as the Power-Point slides suggested, give clear and instant visibility over the inner workings of our agencies, enhance our staff’s lives and make the coffee. Strange I have since felt a strong compulsion to apologise to the many Maconomy users who in those early days found themselves short of utopia. It was more like the Underworld.

Talking it through afterwards with Morton, the Danish Senior Developer, trying to understand what happened between stating our reasonable requirements and the end product, it seems back in Copenhagen they re-thought our needs, and built as only they knew how. Something got lost in translation.

Undaunted, this was the start of the new millennium and things would only get better.

The thing with Maconomy is you’re buying a big box of tricks, and you need to know what you’re doing, have a very detailed spec, patience and a frothy budget.

A range of separate and colourful workflow systems have been invented to fill the many gaps left by Maconomy, Deltek even brought one themselves, but the reality is Maconomy for many ends up an expensive and under-utilised general ledger and accounting system.  Excel reigns supreme.

In all this time, like a long-life battery powered toy soldier, Rebus, now Paprika has quietly and defiantly marched on to a steady beat. A Cobol-based solution developed almost 30 years ago, it was the go to system for smaller agencies and despite attempts by SAGE, QuickBooks and latterly, Xero, the NZ originated cloud system, in many ways it still is.

Paprika has never made a big show of itself, yet through the passage of time and the reluctance of agencies to change systems, it has built a tidy market share of around 1000 agencies, a handful who are global. Despite being clunky and not so easy to use, it’s seen as a safe bet.   

A major drawback though is it is a one currency database system. What this means is as soon as you open your first offshore office, you need two databases. Imagine you have 20 offices in 14 countries. That’s a lot of databases, and even more Excel.  

Today the large networks still angst over systems, systems like Maconomy were seen as a great leveller. Mid-tier platforms for standardising multiple agencies, before moving upwards onto something that allowed greater flexibility in global client billing and reporting hierarchies, and migration to some form of shared service. Indeed this was my own strategy in deploying it into WCRS, now The Engine Group, following our MBO in 2004.

The problem is upwards moves to say Microsoft Dynamics AX or SAP come with their own monumental challenges, and matching price tags. A litany of issues prevail in the network attempts with these systems.

For SME’s, the great hope is the cloud.  

New agile systems, built from the ground up overcome many of the limitations sitting in systems made in the past. Agencies can implement without major cash outlay, retain flexibility and enjoy inbuilt scalability. Cloud usually means seamless and automatic upgrades, allowing users to benefit from continuous system improvements. Never again be threatened with an unsupported version.  

The better cloud solutions have open API’s, allowing true connectivity with other business tools, CRM, CPM, and BI, fully embracing the notion that whilst they may do more, they also do it better. The really good ones integrate all the features of job management, accounting and resourcing – the benefits of which are staggering.

There is still no single panacea for the world of marcoms business management and reporting intelligence, and in a tight margin and competitive digital world, agencies need to find their own differentiators.

Assessing what is important to agencies, the information needs at all levels, the degree of flexibility and autonomy management wants to allow, requires a matching to increased number of suitable systems of today which can offer exactly that. Even Excel now competes with Google Docs.

Which all means it is a really interesting time for agencies.

Overall in the past 20 years agencies have not demanded more, and have been fearful of change, even at risk of continuously adding overhead to get basic information circulated. Accepting compromise has unfortunately ingrained vendor complacency.

Yet for many of the new breed of agency, client demands, the general increase in the variety, scope and speed required of work, and the associated massive increase in the volume of data, compromise and complacency can no longer be tolerated.

The good news is there is now choice. The cloud has brought options that are fully featured, continuously improving, intuitive, easy to use, cost effective and quick to implement.

Agencies fear making decisions on systems, but change should be embraced. As a famous person once said, “Not to change, is to die.”  

So the future for agency systems is indeed bright and can be whatever colour you choose for your management dashboard.

 

How Fit Is Your Agency Solution?

Assess Your Current Performance And Discover How To Transform Your Agency by AccountAbility

THE STATE OF PLAY:  AGENCY LIFE

Today’s agencies are experiencing a very real threat: the increased pressure from clients to do more for less. Add to this the emerging trend of some marketers to bypass agencies and go straight to the source of production and media, or bring the process in-house,  and you have genuine conflict in agency life.  These pressures have a number of consequences. 
It’s natural to respond by working faster, harder and  longer - which more often than not won’t deliver increased profitability or productivity (though it’ll probably get a client off your back for a week or so).

We work with dozens of agencies who are trying to keep pace with rapid changes in the value chain on top of new technology, while still delivering outstanding work for their clients. It’s far from easy and no agency is perfect. 

Click here to download the full ebook

The importance of selecting the right cloud ERP service package

by Rick Carlton

Today’s cloud ERP providers offer a range of service levels in order to ensure the launch, operation and maintenance of their system performs at the highest level. However, in the same way that issues of scale can play against difficulties associated with ERP implementations, problems based on cloud ERP service level can occur leading to lost revenue or unexpected costs of operation.

To help you understand today’s typical cloud service level, here is a short primer on what is generally accepted in today’s market.

Cloud ERP service package options

‘Knowledge-only’ agreements typically offer the following elements; business analysis, operational assessment, systems purchase research and evaluation, and end-to-end roadmap development. The next rung up on the ladder includes ‘core integration’ packages. Packages of this type include more technical, development-oriented or operational tasking such as end-to-end data mapping, enterprise platform identification, analysis and migration, operational implementation, enterprise rollout, module and affiliate systems integration, pre-launch testing and QA, defined support and maintenance and periodic upgrades.

if you have not considered these service packages in a linear fashion, all bets will be off, and significantly more money will be required to effect positive change than perhaps you might expect.

Finally, once your cloud ERP implementation is up and running, enhanced service packages are typically offered. This group of tasks typically include elements such as provider hosting, tailored development, BPO analysis, big data/analytics, and mobility-derived integration.

In each case cloud ERP scale and complexity plays a major part in a company’s cost management and operational decision-making. If you get it wrong, well, you need to be prepared to get your checkbook out.

The implications of your service package decision

In the launch phase, if you have purchased a ‘knowledge-only’ cloud ERP service package, you must accept that the entire responsibility for an ERP system’s viability will rest with your enterprise’s IT cadre. So, if one is running a small shop with limited technical resources, the cost of trying to avoid going beyond the paper analysis stage can demand more money downstream, rather than simply accepting the additional cost of a middle level operational package at the outset.

Recommended reading: ERP software in the cloud - your introduction to cloud ERP projects

In these middle level cloud ERP service packages, the majority of all operational pre-launch and post-launch testing, and initiation elements are included. However, package costs will be relative to the depth of service. Once a system has matured and developed both its own dense data mass and operational character derived by daily use, the scalability of the system and service package will be critical.

If scalability becomes an issue, it may be useful, as well as cost-effective, to purchase an enhanced service package. These can cover the movement of an operational system from one hosted platform to another, the application of additional analysis, or enhancing a baseline system by developing custom code specific to one process or another.

A well understood plan of action

In all cases, these opportunities begin with a well understood plan of action typically based on a multi-year operational schedule, lest the enterprise lose overall technical momentum. The final stage of this planning should involve all that the enterprise and its cloud ERP provider have learned about how and why the company operates effectively, and, in this case, can quickly close the loop on a service decision.

At the end of the day, if you have have selected the correct cloud ERP service package, the expansion of your ERP system ‘should’ be reasonably straightforward. However, if you have not considered these service packages in a linear fashion, all bets will be off, and significantly more money will be required to effect positive change than perhaps you might expect.

How Long Should Your ERP Implementation Take

By Chris Lever

I've been advising agencies on their system selection for many years now, and have led a number of full cycle implementations - that is the design, development, testing and training, go-live and support.

By default, an Enterprise Resource Planning ("ERP") system is for managing agencies, or any people-based enterprise, quintessentially to capture and track time against quoted fees to ensure against over-delivery, hold brought-in third party costs against specific job (or project) records for visibility over what cash has come in from clients, to what's going out to suppliers, and be the secure store of all accounting transactions associated with this and the other activities of the business.  

For many agencies the prospect of upgrading or changing from an existing set-up is fraught with challenges from the cultural resistance to change, to the unknown quantity of what will the vendor actually deliver, in what time frame and at what eventual cost.

It's probably accurate to say a majority of agencies are happy to live with compromise (and spreadsheets) until some driving factor such as the arrival of an enlightened FD with a mandate for change, a vendor contract expiring, or the system version in place is no longer supported, that the difficult questions of a new ERP implementation or upgrade have to be answered. 

So how long should it take?

Well, that does depend on many factors, but here are a couple of examples I can attest to:

UK creative agency, 25 people, new company, so minimal data migration.Duration: 6 hours (4 on-site); System: AccountAbility, a cloud ERP; 1 external consultant.

UK digital agency, 90 people, full data migration, including 1,000 live-jobs.Duration: 3 weeks; System: AccountAbility; 1 external consultant.

UK independent group, 120 people, partial data migration. Duration: 3 months; System: Deltek/Maconomy, a server based system; 2 external consultants.

UK independent group, 650 people (14 offices globally), full development & data migration. Duration: 2 years (and ongoing); System: Deltek/Maconomy; 3-4 external consultants.

UK mid-cap plc, 700 people (20 offices globally), full development & data migration.Duration: 15 months; System: AccountAbility; 1 external consultant.

Of course every agency is governed by their specific sets of circumstances which contribute to making each implementation unique, but at the end of the day the"processes" agencies follow are fundamentally the same.

The dependencies too are all pretty generic, and there's plenty of better documentation than I can provide on the core principles of good ERP project management, but here's a couple of practical tips:

1 System-owner engagement. A strong internal driving force who remains involved and interested is a big factor in helping meet objectives on implementation timing. Someone who understands the system's inner workings, can lead, communicate, gain buy-in and mentor the business all come within this mandate.

2 Experienced project team & competent vendor (or partner) consultants. It helps greatly if the people who work together on the detail and the day-to-day driving forward of the project, know what they're doing and are able to operate within clear guidelines set by the system-owner. 

3 Keeping it simple. Agencies may try and ensure every instance they can think of is covered by the new system, and vendors and consultants will not deter them for complex projects turn into long running projects, with associated fees generated. With few caveats though, I've always endorsed a view of not embarking on substantial customisation, to go simple and "vanilla" first, as any good system will lend itself to modification when it's identified as needed through use.

4 Data in good shape. ERP systems are structured depositories for your business data, and so migrating from a spreadsheet heavy environment will require collating and reformatting of data to fit in these new structures. Agreeing what these structures are can be fraught, and is one of the biggest areas where vendors must be prepared to guide project teams adequately. Most vendors will provide templates for easy upload of data into their system, although likely a bigger challenge may actually be extracting data from your existing system. Tip: Validate the import/export capabilities of your new system. 

Of course if all these remain equal, straight run comparisons on implementation time will inevitably come down to the system itself. 

Server-based systems, like Maconomy, will always take longer. If I can offer an analogy - it's like a large kit (house, car, etc) that comes in a box for which it then has to be put together, piece by piece, each time from scratch. These also need the involvement of IT to agree the hardware & networking specification on which Maconomy will be housed (excuse the pun) and accessed. 

Cloud ERP systems, like AccountAbility, however come pre-defined with best-practice structures, workflows and reporting as determined from experience, which immediately lends itself to rapid implementation. A couple of focused workshops quickly realises a workspace build that meets the agencies need. With browser access, the only involvement of IT is for them to satisfy themselves on the security aspect, then make sure a good broadband connection is available. 

Managing a systems implementation consultancy may suggest we'd prefer long running and complex projects. Well, we're very good at doing them, and like them, sure - to a point.

Our real motivation however comes from getting agencies onto better platforms for growth in much faster time frames, to get their data joined up and them benefiting from the visibility on how their business is performing, and able to make the adjustments they need to be more profitable. This for us means happy clients, and stronger, longer term relationships. 

Final point then, balls on the line - how long should an ERP implementation take?

My rule of thumb. A 100-person agency, going AccountAbility, will be live within one month. If you're going Maconomy, I'd have to have a look and give you a quote. 

 

Systems Are Go

The management of corporate workflow is increasingly becoming a concern.
Molly Pierce investigates the solutions

Systems pursue us throughout our lives. They can be productive or restrictive: but for corporate agencies and their clients, they're very necessary. The management of corporate workflow is highly important, as both a preventative measure and a solution to tangled situations.

It's tempting, particularly early on in an agency's life, to believe that corporate workflow management is better left up to the big guys. "Many agencies with the talent to conceive and execute outstanding creative work leave their financial systems upgrade to a later stage – typically when their first major clients start demanding greater analysis on the management of their accounts" says Chris Lever, MD of AgencyDNA.

However, this approach of waiting to react to demand for management software is misguided, Lever believes. "No matter what stage of a project, or how big or small, agencies should not compromise on their information systems. It's fundamental to being in control. It's not untypical that until this point [of upgrading] all client budgeting, report and analysis is done in Excel and, with financial data views not coming directly from the system, it is this disconnect which carries risk."

AgencyDNA is a consultancy which specialises in systems that improve planning and management at creative communications agencies. It recently announced an exclusive partnership in the UK and Europe to distribute AccountAbility, a new cloudbased management solution, which can integrate all of an agency's financial and management information – meaning fantastic accessibility and no need for costly, space-filling servers.

However, it isn't just in account management or budgeting where systems for managing projects are essential. Leif Skogstad, commercial director at the corporate communications agency Addison, told me that Addison has been offering remote access systems to its clients for 14 or 15 years.

Addison produces annual reports for many of its public company clients - a labour-intensive and timeconsuming process. It will never be an easy task: annual reports go to investors and analysts, and are full of crucial detail. Errors or even mis-steps can severely damage a company's reputation and therefore its bottom line.

"These reports are 250 pages, and they take three or four months to produce, with as many as 15 people needing to edit the document," says Skogstad.

"In fact, it's going up to 19 users with a client in the next few months. But we're working with people whose main occupation is not the efficient production of a document - nor should it be."

Recently, Addison has switched over to a new system for managing the editing process of its reports, a Swedish service called CtrlPrint. Addison assumes the cost of installing CtrlPrint and its InDesign and InCopy plug-ins on its clients' systems, because the benefits to the overall management of workflow far outweigh the expenditure.

"The main point for us is to be flexible," says Skogstad. "We would never tell clients how they ought to work, but using this system definitely makes the client's life easier." Of all the clients that have made the transition with Addison to using remote editing on their annual reports, not a single business has then reverted to tradtional methods. CtrlPrint has had some customers shy away from the system, but its feedback is for the most part extremely positive.

"It used to be the case that you would agree on a number of proof cycles, which was labour intensive. I've seen account managers on the phone to clients for four hours at a time going through a document section." Previously, reports were marked up, often by hand, then scanned or delivered back to Addison. Now, CtrlPrint allows team members access to edit the specific sections relatable to their function, then upload the edited versions back up to the system.

"The first benefit is that you're not tied to a cycle of proofs, so certain sections can go through 15 or 16 rounds of amendments if needed. The amendments can be made and approved within an hour, rather than waiting for the next proof cycle – so it consolidates the process." The second benefit, according to Leif, is in the time saved; the new system also allows for greater accountability.

"It's improved control over the document itself, because all changes are tracked and the version history shows who's made which changes when. This in itself helps to apply internal rigour," he says. "And you can control whose changes are accepted, and who has read-only access, and who has editing access for each section, as well as switch these security levels during the editing timeline."

Lever also brings up increased levels of control as a reason why such software is crucial for a business. "Without integration... the time spent on the job may not be known, the agency can lose sight of the third party cost spend, and very soon the expected profit and capital working positions are exposed. Integrated systems provide visibility over client jobs at any stage." The new control levels are also a tangible benefit to clients, as well as the contribution to a job's overall profitability.

A major plus with AccountAbility is its mobile capability. Lever says this is crucial: "Like most industries, agency people increasingly expect to be able to access their tools on their phone or tablet, to view or update details such as doing a timesheet, wherever they are. Accountability has iPad/ iPhone capability and is developing an HTML5 interface to be used across any browser." And the straightforward web delivery system of CtrlPrint is attractive to Addison.

Although these systems do two very different tasks – and in fact, there are probably as many systems for managing corporate workflow as there are processes which need managing – the benefits to companies are transparent: they provide ease of use, increased visibility and accountability, straightforward interfaces, and flexibility. It seems likely that before long, comms agencies won't know where they were without them.


Article Source:
Communications Magazine
Wednesday, 02 January 2013