You Were Never Made to Be ‘Productive’

Compared to people in other industrialized nations, Americans work longer hours, take fewer vacation days, and retire later in life. Busyness, once seen as the curse of the disadvantaged, has become equated with status and importance. Our work increasingly defines who we are.

“Godly rest (distinct from play, relaxation, or sleep) is inextricably tied to our identity as children of God.”

The solution perhaps is to be “Lazy Intelligent”?  That sounds like something an unsuccessful, lazy slacker would say, isn’t it? Actually, it’s the opposite. One of America’s most influential and controversial science fiction authors Robert Heinlein uttered these words during his time. Despite his nod to laziness, Heinlein went on to pen hit titles such as Starship Troopers and Stranger in a Strange Land.

Productive laziness is not about doing absolutely nothing at all. It’s not about just sitting around and drinking coffee or engaging in idle gossip while watching the non-delivered project milestones disappear into the horizon. In fact, this behavior would lead to a very short-lived project management career.

Laziness Is Not Synonymous with Stupidity

Instead, productive laziness should be viewed as a more focused approach to management. Adopting this mindset means concentrating efforts where it really matters, rather than spreading yourself thing over unimportant, non-critical activities that in some cases don’t need to be addressed at all.

According to the Pareto Principle — Also Known as the “80/20 Rule” — 80 Percent of the Consequences Stem from 20 Percent of the Causes.

While the idea has a rule-of-thumb application, it’s also commonly misused. For example, just because one solution fits 80 percent of cases, that doesn’t mean it only requires 20 percent of the resources needed to solve all cases.

The principle, suggested by management thinker Joseph M. Juran, was named after Italian economist Vilfredo Pareto, who observed that 80 percent of property in Italy was owned by 20 percent of the population. As a result, it was assumed that most of the result in any situation was determined by a small number of causes.

Rest Is at the Center of God’s Design

Every smart but lazy person should consider the 80/20 Rule each day. For managers, the principle is a reminder to concentrate on the 20 percent of work that really matters.

Contrary to belief, 80 percent of success is not just showing up. In fact, only 20 percent of what you do during the day will produce 80 percent of your results. Therefore, it is important to identify and focus on that 20 percent during the working day.

Project Journal5

When genius and laziness meet, the results can be magical. Being just the right combination of smart and lazy can bring you to have a real edge over others. Interestingly enough, smart lazy people are generally better suited for leadership roles in organizations.  These people make great strategic thinkers and leaders. They do things in a smart way in order to expend the least effort. They don’t rush into things, taking that little bit of extra time to think and find the shortest, best path.

They  question, contradict, and show dissent against inefficient methods or unnecessary tasks.

“Whenever There Is a Hard Job to Be Done, I Assign It to a Lazy Man; He Is Sure to Find an Easy Way of Doing It. — Bill Gates”

Bill’s not the only guy, who believes that laziness doesn’t necessarily have to be a bad thing.  German Generalfeldmarschall Helmuth Karl Bernhard Graf von Moltke was the chief of staff for the Prussian Army for 30 years. He is regarded as one of the greatest strategists of the latter 1800s among historical scholars and is the creator of the more modern method of directing armies in the field.

Moltke observed his troops and categorized them based on their intelligence, diligence and laziness. If soldiers proved to be both lazy and smart, they were promoted to leadership because they knew how to be successful with efficiency. If soldiers were smart and diligent, they were deployed into a staff function, focusing on the details. Soldiers who were not smart and lazy were left alone in hopes they would come up with a great idea someday. Finally, soldiers who were not smart but diligent were removed from ranks.

Like Moltke’s army, the lazy manager is all about applying these principles in the delivery and management of work. You’re likely not stupid since you’ve landed the management position, but how are your lazy skills? Applying smart-lazy tactics will not only allow your work to be more successful, but you will also be seen as a successful individual and a top candidate for future leadership roles.

Think return on investment (time spent versus money earned ratio) rather than busy work and  don’t restrict yourself to a certain way  of doing things just for the sake of the status quo.

These people make great strategic thinkers and leaders. They do things in a smart way in order to expend the least effort. They don’t rush into things, taking that little bit of extra time to think and find the shortest, best path.

In the wise words of Bill Gate’s and American automotive industrialist Walter Chrysler, “Whenever there is a hard job to be done, assign it to a lazy man or woman for that matter; as he or she is sure to find an easy way of doing it.”

For an overachieving people-pleaser like me, thinking of rest as an innate part of who we were created to be—not as a discipline or something to be earned—is compelling. It is yet another form of God’s infinite grace, one that’s needed today more than ever.

Co-Author Peter Taylor

Described as “perhaps the most entertaining and inspiring speaker in the project management world today”, Peter Taylor is the author of two best-selling books on ‘Productive Laziness’ – ‘The Lazy Winner’ and ‘The Lazy Project Manager’.

 

66% of IT Projects Fail

Is Britain a nation of slient Christians?

Only one in three software projects will turn out to be successful. According to Standish Group’s 2015 Chaos report, 66% of technology projects (based on the analysis of 50,000 projects worldwide) end in partial or total failure. More surprisingly, these statistics have been the same for the last five years, the report shows. Furthermore, 17% of large IT projects go so badly that they can threaten the very existence of  a company.

On Average, Large It Projects Run 45% over Budget and 7% over Time, While Delivering 56% Less Value than Predicted

Despite such failures, huge sums continue to be invested in IT projects and written off. For example the cost of project failure across the European Union was ┚¬142 billion in 2004.

It Projects Always Come with an Element of Risk, but There Are Huge Gains to Be Had If We Can Just Avoid Some of the Factors That Contribute Frequently to Project Failure

What makes a IT project successful, though?

According to the Standish Group, a successful project is on time, on budget and has satisfactory results (value, user and sponsor satisfaction, and meets target requirements). Other measures of success are widely known and accepted as true such as getting requirements right, providing effective leadership, and having full support and engagement from sponsors and users. Without these, it’s unlikely that any project would succeed.

But there’s more to success than what is widely known and, apparently, rarely followed. To reduce the risk of failure for your tech project, here are  six key actions to take on the road to success.

1. Executive Vision and Involvement

Without a Executive Senior Sponsor Its Easy for Projects to Fail with the Organizational Resistance That Accompanies Large Change

Executive involvement is a primary variable in predicting the success of an IT project.   Having a leadership team aligned across an organization articulating the purpose, value, and rationale for a project goes a long way towards getting stakeholders and end-users pulling the proverbial rope in the same direction.

2. Have a clear view of scope and timetable

Oftentimes, a tech project flops because its developers fail to plan and rush forward with  an idea. However, some project  managers plan so meticulously that they end up falling behind and lose momentum. The best approach is somewhere in between.

Interviewing team members, documenting requirements, prioritizing what is “mission critical” versus “nice to have,” getting agreement across stakeholders can feel like a never-ending cycle.   As a result, requirement gathering has fallen out of fashion with many organizations  in the past few years.

However, the ideal starting point for a successful technology project is to have a set of fundamental requirements with sufficient detail to develop against.

Requirement Gathering Is Labour-intensive and Challenging but Remains the Roadmap and Measuring Stick for Software Projects

This approach allows you to maintain sight of the business benefits as well as engaging stakeholders and responding to their feedback.  In combination with a  clear business case, a  well-defined set of requirements also simplifies design and testing, two areas where projects tend to go  sideways.

Ensure that requirements for the project are clearly defined and agreed upon among stakeholders and that you have a way to track, measure, and manage changes in requirements as appropriate during the project.

3. Define how you will deliver

When it comes to delivering a major project, one size does not always fit all. All products are customizable to some degree, so what might have worked  in one company may not work in another company.

That being said, why reinvent the wheel if it’s already proven successful?  Sometimes it  can be more beneficial to  use an existing  off the shelf solution. Whichever direction you take,  choose the delivery mode that works best for your company.

4. Risk Identification and Management

Every project has risk and  there are many  factors out of your control. People leave the organization, for better or worse, leadership changes,   budgets get cut, however, many risks  to projects can be mitigated or even eliminated with some forethought and on-going management.    For example, do you have the resources you need to deliver the project (resource risk).   Are project goals clearly understood and requirements clearly defined (scope risk).   Do you have a realistic project plan and timeline (time risk).

Mitigating Risk Is a Combination of Science and Art, and Always a Balancing Process

5. Test your product again and again

A technology project is something that should overall support your business. It should not be something that dictates and forces you to  change your operations. If this is happening, you should shift gears and focus on tweaking the technology, rather than lowering expectations and adopting less ideal requirements.

Adequate testing is a must for any tech project. While some features may be fine with automated testing, the best approach is to have a dedicated testing team. Testing activities should mirror those with the development team throughout the project’s lifetime. With thorough testing, a project should deliver with less design flaws or missing requirements.

6. Prioritize simplicity and performance

Developers often leave the external look and feel of a product to the wayside thinking these things are not necessities for the consumer to enjoy. However, user experience is absolutely critical to the success of the project.

Developers must consider things like storage, network requirements, processing speeds and overall performance in order to satisfy the customer. If users are going to have to wait for an extended period to allow information to load, there must be a good reason for the wait, otherwise they won’t return for future products.

Simplification and Improved Efficiency Is What Adds Value

Ultimately, using the product should be a smooth and intuitive experience. Additionally, tools and alternative routes must be placed logically without being intrusive. The process can be complicated, but the finished product should emit simplicity. After all, that’s what makes companies like Apple so successful. Simplification and improved efficiency is what adds value.

A Day in the Life of a Project Manager

Managing Daily Routines: A Day in the Life of a IT Project Manager

We all know that project managers are responsible for managing projects through to completion while remaining on time and within budget, but how exactly do they do it? What does a typical day look like for a project manager?

Here’s a sample of what a typical day might look like for a project manager.

The Early Bird Gets the Worm, Success Comes to Those Who Prepare Well and Put in Effort

8.30  am: Starting the day
After settling in for the day’s activities, it’s time to plan out the day. Start up the computer, email clients, draft team schedules, organize time sheets and  create the to-do list.

To-do lists help managers and their teams stay on track. If a manager notices that one team member has yet to deliver an assignment, they can address this issue first thing in the morning; otherwise, delays can build up and affect the project. Likewise, lists help managers see the next course of action for projects.

9:15 am: Time to get moving

Efficiency is a must and there is no time to be wasted in project management. After a quick review of project plans and to-do lists, the manager must be prepared to get his team moving right away.

Round up team members, review the project’s current position and emphasize the next course of action. In order to get the team moving on assignments, strong project managers set deadlines throughout the day.

Morning team meetings are also necessary to make sure each member understands the project and their assignments. It’s also a time to answer any questions for clarity or to get feedback or concerns from individuals.

While daily group meetings can be important, they are not always necessary and can be counter-productive. If the team is on the same page and everyone is ready to tackle the tasks of the day, spend a short period re-grouping so that the team can get on and complete their assignments. There’s no need to spend hours planning and reviewing.

10 am: Meetings, meetings, meetings
More than one project manager will be  more than likely  in the office  and they will all need to work together for the benefit of the programme. This is why meetings with other managers and higher ups are necessary in a project manager’s day.

Meetings allow each project manager to go through the status of their respective projects and to track the weekly schedule and other deadlines. It is also a time to address any business-critical tasks that might come up.

It’s worth considering that only 7% of communication is spoken. The other 93% is made up of tone (38%) and body language (55%). So although facts and figures are easily communicated via email, letter or phone, an actual discussion or negotiation is best handled where you can see the other person and therefore are able to see for yourself what their tone and body have to say on the matter.

10:30 am: Tackling the small stuff
Meetings will be on and off throughout the day for project managers, which is why it’s important to tackle the small tasks in between appointments. Small tasks include wrapping project reports, booking future meetings, answering correspondences with other colleagues, reviewing items and team reports among other things.

It’s also important to schedule post-mortem meetings with the project team  to review the success of  projects  in order  to apply any  lessons learnt to future projects.

11 am: Project kick-off meeting
When one project ends, another begins, which means it’s time for yet another project kick-off meeting. Kick-off meetings can take on various forms, depending on the type of business. However, they all share the same basic needs.

Every individual involved with the new project should be in attendance and have the latest version of project specifications in written form. As project manager, it might be wise to send this to team members several days before the kick-off meeting to ensure everyone has time to review.

During a kick-off meeting, it’s important to review the overall goals for the project, both commercial and technical details, break down functional requirements, and spend time for discussion and questions. By allowing team members to communicate questions and share ideas, it opens the lines of communication and may bring up potential concerns that might have been missed in the initial planning stages.

Conclude kick-off meetings with a definition of the next steps and be sure individuals are aware of deadlines and their assignments.

11:30 am: Reviewing project specs, budgets and scheduling submissions
Other important tasks to tackle in between meetings include reviewing specifications and budgets and schedules for future projects. If a project begins that day, now would be a good time to  apply the  finishing touches to the project documentation before presentation and approval.

When it comes to establishing project estimates and budgets, a project manager must bring all of his experience into play in order to create a realistic budget that includes wiggle room for factors such as project complexity, team experience and skill levels, stakeholders involvement, time needed, third-party services needed, and contingency allowances among many other things.

It’s Not Easy to Squeeze in a Lunch Break, but It’s Often Necessary for the Project Managers Health and Sanity

12 pm: Lunch
In the midst of the seeming chaos that is project management, be sure to fuel up for the rest of the day’s work. Lunch is also a great span of time to check in with team members to make sure they are still on target for later-day deadlines.

2 pm: Launching the next project
After digesting lunch, it’s time to launch the next project. Get the whole team ready to go live and present the project to the client and begin testing aspects of the project in a live environment. It’s a time to spot problems and address them and review schedules and deadlines and other project needs.

3 pm: Time for everything else
The final two hours in the office are spent addressing everything else on the project manager’s plate. A project manager must be good at multi-tasking and whatever duties couldn’t be accomplished throughout the day are reserved for the final hours. Most of the time, lower priority tasks are reserved for afternoon hours. These tasks could include project update meetings with various departments, logging finances, reviewing monthly project schedules, approving time sheets, writing weekly reports, sorting purchase orders and communicating with suppliers. There are so many other small to-do list items that project managers are responsible for, but are often overlooked.

Spending Time at the End of the Day as Well as the Beginning to Review and Plan Will Only Help You Succeed as a Project Manager

5 pm: Review the day, plan for tomorrow
Before heading home, review the day’s list and what’s been accomplished. Anything that has been added or was left unfinished should be scheduled for the next day or sometime throughout the week. Reflect on your team’s work and clear the email inbox. Use a filing system that makes sense for you and be ruthless about deleting stuff. The beauty of an empty inbox is a thing to behold. It is calming, peaceful and wonderful.

Project Manager or Scapegoat?

You Need to Stop Pointing That Finger

Big Project Failures Claim Their Victims in Spectacular Fashion

You’ve just been assigned a high visibility failing project  and  you’re working round-the-clock to get the work to the client on time, despite the fact that the job bears barely any resemblance to the project  you initially discussed. The  scope keeps creeping, the risk  and issue alerts are coming in thick and fast, the project is already  two months  past the original deadline, the clients are getting antsy even though they’re yet to provide you with various key pieces of information in order to baseline the project.  Is this your chance to shine  and showcase your skills?

If You Don’t Know Where You’re Going, You Will Probably End up Somewhere Else – Laurence J. Peter

If you manage to turn the project around and the project is successful, you will attract many fathers. However, if the project fails, you will probibly be  offered up as the  sacrificial lamb (scapegoat),  there is absolutely no way around it.  A  high percentage of projects fail to deliver useful results, that’s a  fact.

Project managers are  regularly blamed for schedule delays and cost overruns for projects they inherit by no fault of there own, however, in most cases, the fault for such issues rarely lies with just one person.

Sufficient data has been gathered to indicate that blockers such as unsupportive  management, senior sponsorship or low  resource availability are as much to blame for project failure as ineffective stakeholder management or poor communication.

Capture  all decisions

The only way to protect yourself is to ensure that you capture all decisions made in the project. In most cases  many of these decisions  will have been made by people above you. While you can influence decisions made by people under you. Get into the  habit  of building a dashboard early in the project and updating it each week with actuals.  Also consider using a  standard repeatable technique to analyse the health of your project.

Constrained resources

If you are in a project where resources are constrained, clearly outline the resources that you require to deliver the project in terms of time, scope, budget, risk  and  quality. If resources are pulled from your project, clearly articulate the affect of that in delivery terms and measure that to time delayed or cost added.

Risk and issues register

Operate  a strong risk and issue register,  ensure  it is both visible  and assessable so  your team can  actively participate in updating it.

Stop  the project

Always remember, cancelling the project is not always a failure. There can be many reasons why the project may no longer be desirable now. If you have done your job well, you can be really successful by ensuring a project does not continue to meander along, wasting time and money when there is no possibility of completing the project.

Organisational change management

Unfortunately, the same can’t be said when there are organisation change management issues.   While there are a  few project managers who feel their jurisdiction ends at the triple constraint, most now  understand the need to achieve the expected benefits from their projects.

So when is it fair to blame a project manager for poor implementation of a  project’s deliverables,  this is assuming that they were employed at the beginning of the project?

  1. If they didn’t perform good  stakeholder analysis during the project initiation stage as well as at regular intervals.
  2. If they turned a blind eye and deaf ear to factors that could impact value achievement
  3. If they didn’t insist on a clear communication strategy and progressive information sharing with relevant  stakeholder groups.
  4. If they didn’t engage influencers from key stakeholder groups throughout the project lifecycle.
  5. If the organisation management deliverables were not built into the project’s scope definition and work breakdown structure.

Assuming the project manager was appointed at the start of the project and had undertaken  all of the above, what are invalid reasons to blame the project manager  if the project failed?

  1. A lack of timely resource availability or commitment by the organisation
  2. Directives to the project manager to not engage certain stakeholder communities
  3. Ignorance by senior sponsors to management risks raised by the project team
  4. A management decision  that is too bitter a pill to swallow in spite of how much it has been sugar coated

Have any comments or stories that could help to expand this article?

Prefab Comeback

Prefab  housing suffers from bad stigma due to the fact that some people saw the prefabs as ugly and characterless, and were afraid they would become slums – hardly the promised housing fit for heroes  following the second World War. However, building homes from pre-made parts can save time and money.  The term prefab or prefabrication often evokes thoughts of poor construction, substandard living conditions and a long-standing “temporary” solution.

Prefab dwellings are making a comeback driven by a lack of affordable housing, a rapidly growing economy and changing demographic trends.  

Methods Methods of Construction (Mmc) Offer Significant Potential to Minimise Construction Costs

The term ‘Modern Methods of Construction‘ refers to a collection of relatively new building construction techniques that aim to offer more advantages over traditional construction methods. Off-site construction (OSC) is a modern method of construction, based on off-site manufacturing of building elements.

With exponentially lower construction costs, quicker construction, reduced  labor costs and having the ability to achieve zero defects, MMC is gaining a lot of attention as the  potential answer to the UK’s housing crisis.

In a valiant attempt to strip away prefabricated housings’ bad rep are MMC with contemporary sleek designs, and constructed to withstand the test of time. MMC housing has the capability to deliver both quality and quantity housing to the tune of ‘ £50,000 per unit.

MMC units hold the promise of being extremely  energy efficient and environmentally sustainable. Many versions of MMC take into account how to utilise natural resources and reduce each unit’s carbon footprint. In addition, MMC also addresses environmental concerns by creating much less waste than a standard brick-and-mortar project. While it is plausible that a traditional build could hire a waste removal company who would have the ability to recycle up to 90 percent of the construction waste; with MMC projects, this will automatically happen.

M-house (pronounced “mouse
M-house (pronounced “mouse”)

There have already been a number of successful examples of MMC housing constructed in various parts of the United Kingdom. The M-house (pronounced “mouse”) is designed and constructed to last an upwards of 100 years. While Architect Alford Hall have created quality MMC apartment buildings proudly showcasing a patio and private entrance for each flat.

Architect Alford Hall
Architect Alford Hall
Compass House by AHMM
Compass House by AHMM

While many of the MMC homes  are still in their early years the upkeep and maintenance will be reduced by 50%  since the OSC  process lowers the risk of non-conformities.

MMC homes are being fabricated and designed to accommodate many different lifestyles, such as, two-story homes, tall six-story apartment buildings, single-family homes and log cabins are all available options for families looking at MMC.

While there is a plethora of design options available all MMC  OSC  projects have a common theme. The internal workings of the homes are fabricated off-site, while only the “outer skin” comes to fruition on-site. To even further streamline the process, it has been suggested that having a “catalog of pre-selected materials increases supplier relationships and makes the design process more streamlined.”

With the small sample available with progressive MMC systems, it is currently reasonable to conclude that using modern methods of construction to build homes can cost more than traditional home building procedures; due to the need for specialised MMC design consultants. However, outside of costs, MMC remains a faster home building method than traditional brick and block house building and is slowly  becoming a relevant front-runner to answer the  UK’s housing shortage.

 

As seen on