Google’s announcement that self-driving cars will hit the road this summer is heating up the “people vs. software” debate.  Is this the start of safer roads and drivers?  Or will it, as some experts fear, begin a slow takeover by our AI overloads?

No matter how complex the program, it’s unlikely any software will ever completely account for the X Factor in driving. (A lighting strike? Tornados? Flooding?)…not to mention the X Factor combined with the human element, such as modifications of the software by the adventurous or curious…or the malicious.

In the project management world, however, the debate seems settled in many quarters.  Time and again, PSI trainers have encountered inexplicable – and sometimes undeserving – reverence for project management software.

PSI views software as the servant, not the master. We’ve developed an add-in for Microsoft Project that puts users in control of their schedules.  It produces a more stable schedule because task duration, resource assignments and status do not change without the user’s input.

After all, if Google adds steering wheels to its self-driving cars, shouldn’t project managers be able to take the wheel in their management software, too?

Happy summer. Your project is about to get disrupted.

Summer brings vacations, kids free from school, office summer hours, and weddings.  It disrupts the flow of business (up to 20 percent decrease in productivity and a 13 percent increase in project turnaround times).  Global projects are particularly vulnerable to The Summer Syndrome, since many workers abroad often vacation at the same time, in August.

In the U.S. not everyone will vacation at the same time…but that’s a mixed blessing. A string of vacations taken throughout summertime creates a ripple effect as the project progresses. Decision makers, team members, vendors, consultants, shippers, payment processors – every function and business segment is affected.

That’s a compelling argument for the Project Success Method’s duration based project planning.  Our seven-step duration estimating process helps team members devise real-world timeframes (in which people go on vacations, for instance), while our add-in for Microsoft Project give managers more control of the schedule.

Of course project managers must still monitor for schedule slippage to prevent the Summer Syndrome.  However, the right tools and realistic scheduling can help make projects and teams have it “made in the shade” clear through to project completion.

Even if PSI’s headquarters weren’t in Atlanta, we’d still be fans of the Hawks.

They gave us an exciting season – and gave the Cavs a close call in Game Three despite injuries.  They also brought to life the importance of teamwork. (Earlier this year, the NBA named the Hawks’ entire starting five “Player of the Month.”) In the Eastern Conference finals with the Cavaliers, the contrast could not be starker:  a team playing as a unit, vs. a team with a Superstar – the Superstar – LeBron James.

They were swept by the Cavs, but they succeeded in other respects.  They demonstrated that real teamwork, with no one player bigger than the rest, sharing the ball, communicating, and helping teammates is a powerful strategy.  Injuries and questionable behavior from opponents took a toll, but this is a young team committed to a long-term strategy.

That’s a lesson that project managers trying a new approach might take to heart – institutional success is a long game that requires a long-term commitment.   In project management, that’s a compelling and relevant lesson. A superstar is a phenomenon, but everyone in project management works on a team.

We can’t wait till October.

One distinctive – but misunderstood – aspect of the Project Success Method is the importance of frequent, face to face meetings. Frequent meetings are too often considered productivity-killing time-wasters – there’s even an app for that.

Yet, time and again, we’ve found that face to face team meetings are the best way to get things done, especially if the ‘mechanics” of the meetings are right:

•  Schedule consistently, using the same dates/times. Apps can help; a comprehensive roundup is here.

• Be brief. After 45 minutes to an hour, focus plunges.

• Create an agenda, stick to it, lead it and end it on time.

• Stay on track. Note essential, but non-agenda concerns, and follow up after the meeting.

• Refreshments? Beverages yes; food no.  Dehydration hampers focus, but it plummets if attendees sit still for an hour in a crowded, windowless room while digesting lunch.

• No electronics or side discussions.

• Air concerns, questions, problems and solutions…but not complaints or whining.

These “mechanics” help create a successful meeting, but proper planning and people skills are key.  Together, these elements can make meetings less of a necessary evil and more of meeting of the minds.

There’s an interesting message hidden in the offerings at the upcoming Project Management Institute’s World Congress.  Classes in Technical Skills comprised only 18 of the 65 classes listed by “content aim;” the largest individual class category was not about Agile, or Change Management – it was “Leadership Skills for Project Managers, Program Managers and Portfolio Managers.”

It affirms our conviction, backed by a survey quoted by PMI, that people skills are a major factor in a project manager’ career.

Trends in leadership theories abound; Googling “Business Management Leadership Theories” yields nearly two million hits.  It’s easy to get tangled up in Theory Overload –

Management By Walking Around, Emotional Intelligence, and others flourish.  Whatever the theory, though, our years of experience confirm that the best project managers:

-Recognize that the most important element in a project is time

-Earn and maintain the trust of the project teams

-Inspire the team members commitment to the project with mutual support and individual accountability.

Those three points work together and will work with just about any theory, yielding successful projects and successful careers.

Looking at lists of ‘epic product fails” it’s easy to wonder how experts in well-established companies could miss such obvious problems – snacks that cause gastrointestinal distress, for instance, or a complete misstep in brand perception (Yogurt shampoo?)

Now, though, product success could also hinge on identifying and satisfying new ‘must haves” in product attributes. Industries today wrestle with benchmarks unheard of twenty or even ten years ago. The ground rules for product – and project – success are changing to include new “must haves” like:

–sustainability in products and processes.  The Global Development Research Center even created a program for Environmental Assessment as a project management tool.

-confidentiality of personal data.  Three out of four Americans say they won’t use Google Glass because of privacy concerns.

For project managers, this means rethinking project charters with a more expansive collection of stakeholders, and a wider description of constraints, assumptions and risks.  We teach an extensive pre-planning effort (we call it the Project Success FirstStep Process^®) that covers forming the team, doing the ‘pre-work,” creating the charter (via an extensive, in-person process), and getting it approved before starting the planning phase. Everyone has a chance to put their arguments on the table.  The result is a charter, and a clear set of marching orders, that is approved by stakeholders and in line with what the customer wants.

That way, their projects or products can stay ahead of the Next Big Thing…instead of getting run over by it.

Although it’s Spring, the No Pants Festival has nothing to do with Spring Break and everything to do with an evolving management trend – the remote management of digital nomads. I call this type of workplace management “Radical Flexibility.”

The newest take on Radical Flexibility is ROWE (Results Only Work Environment).  The ideal ROWE workplace eliminates office norms: no set hours, no required meetings or office hours unless required to do your job.  The only measure of value is the results.

More accountability and less micromanaging are Project Success Method bywords, and some studies suggest positive impacts…but the underlying assumptions are less promising:

• you could get so much more work done if you didn’t have to bother with other people

• structure is a cage

A collaborative environment needs some structure – how can people work as a team without set hours? – and a meaningful team can’t be formed with people only known to each other as an email address.

The Project Success Method offers a better, hybrid alternative.  Our techniques encourage in-person meetings to strengthen mutual support, collaboration and commitment to projects – but individuals are free to decide whatever pace or solutions work best. The Method has worked for small new product launches and large-scale, mission critical, time-sensitive, cross functional projects across an entire enterprise – while combining accountability and freedom for individuals, teams and managers.

Now that’s what I call Radical.  But no, it’s not pants optional.

A survey of 32,000 employees revealed that people who met with their managers up to six hours a week were more inspired, engaged and innovative at work. That confirms PSI’s preference for in-person, biweekly team status meetings to shift the Worry Curve.

We know it’s difficult to make time, coordinate schedules, and reserve the room. However, consider the pitfalls of relying solely on electronic status reports – for project managers and teams:

• It encourages procrastination:  Emailed status reports and updates sit in an inbox with other email – easy to overlook or put off. It doesn’t command the attention a meeting would.

• It discourages group problem solving:  Electronic reporting deprives the project of the collective insight and support of the entire team when problems arise.

• It hinders accountability: The biggest problem electronic reporting creates is enabling team members to avoid public accountability for their tasks by hiding behind email.

In-person meetings create team commitment to the project, to each other and to their own roles in the project, while project managers find it easier to monitor progress, see deviations from the plan and tap the insights of the whole group to find solutions.  Being in a room together drives accountability, results, and a sense of community.

It’s a lot better than hiding behind an email.

Andy Rubin, the creator of Android, is launching an incubator for innovators…and it reminds me of a familiar mindset.

His Playground Global LLC will provide support and advice to tech startups making devices for consumers or businesses. This “studio” lets inventors do the fun stuff (creating new products). Playground handles the operations – the scut work, so to speak.

I think “scut work” needs an image overhaul. It’s how Things Get Done. Improving how Things Get Done is a worthwhile investment – but you wouldn’t know from some responses project managers tell me they get when pitching Project Success Method training to senior management:

“It’s just more overhead”

“We bought software to handle that”

“How much can anyone learn in just two days?”

“It’s micromanagement”

It’s like the joke about making politics and making sausage – but it’s the “scut work” that takes a new product from a blank screen to a sales floor. Improving that process is a worthwhile investment that’s paid off for our clients in time and money again and again – and saved weeks of panic-driven overtime by team members caught in a time crunch.

Suppose your car needs an oil change. You visit two garages on Monday looking for estimates. Garage One quotes $50; Garage Two quotes $50. Both say it takes two hours.

You leave your car at Garage One, go to a movie, and return two hours later to pay and drive away. Three months later you try Garage Two. You return from the movie. There’s an oil pan under your car. The mechanic is working the register.

“I need my car,” you say.

“It took an hour to prep and drain the oil,” the mechanic says as he rings up someone. “Now I’m on the register for the rest of the week. I’m not sure when I’ll get to the remaining hour.”

No one would accept this scheduling for a car. Why accept it in a project?

Relying on resource hours over task duration is one of my project management pet peeves. Methodologies that rely solely on resource hours don’t adequately predict when things will actually get done.

Managers and teams that go through our training get practical experience in the kind of scheduling that tells them when they can take the next step and when the job will be done – ahead of schedule, too. In project management, as in life, knowing how long a task takes – even a simple oil change – is insufficient. You need to know when you can drive your car.   It’s the only way to get anywhere, on the road or in your career.