Showing posts with label Project management. Show all posts
Showing posts with label Project management. Show all posts

Friday, December 5, 2014

How to get the most out of your IT talent

 
As the spotlight on cost reduction has dimmed, IT has picked up plenty of new directives: to deliver business agility, drive innovation, and increase its value to the business, to name a few. Yet at the same time, IT remains responsible for all the tactical and operational activities it has always performed, such as keeping systems running, delivering new capabilities, and securing intellectual property and corporate data.
For CIOs and IT leaders, the management challenge is how to help IT employees break the tactical habit and use their strategic skills more effectively. We asked for advice from three tech professionals with different perspectives on IT talent. Their expertise can help IT leaders who want their teams to work smarter and be more engaged. Some of the tactics can be adopted without a lot of investment, while others require outside help or more significant cultural overhauls.


Before/after coffee tasks

Time management is a logical place to start. A capable leader can help his team make time for higher-level tasks that will increase the value of IT to the business. But good IT leaders require cultivation.
Most IT professionals are what I call accidental managers."Most IT professionals are what I call accidental managers,” says Eric Bloom, a former CIO and current president of Manager Mechanics, which specializes in helping companies develop IT leadership talent. Many IT managers were promoted because they were good at their former jobs – even though their new jobs might have little to do with their past experience.
Eric Bloom, a former CIO and current president of Manager Mechanics
"Hey, you're the best techie, congratulations," Bloom says. "You didn't go to school to learn what we're going to ask you to do. All of the things you did that made you such a star employee and made us want to promote you -- none of that is applicable to what we're going to ask you to do. And, the job opened because we promoted someone into the job last year, with a skill set somewhat like yours, but they failed miserably and we had to fire them. Welcome to management."
New IT managers have to adjust to a role of delegating vs. building. "Your creativity comes in maximizing the efficiency of those working for you,” Bloom says.
One delegation technique Bloom has devised is what he calls zone-based staff prioritization. It’s built around the idea of being in the zone – when people know what needs to be done, aren’t distracted, and are motivated to complete a task, they can be more productive, more innovative, and do a better job. "Sometimes people are at their best. Sometimes they're alert but not creative. Sometimes they can do things but they're not really open to challenge. And sometimes, there are things they can do as long as they're not asleep or semi-comatose," Bloom says.
Bloom’s technique aims to prioritize people’s to-do lists by zone levels, with the most strategic tasks being tackled when people are performing at their highest.
"When they're at the top of their game, they should be doing software development, writing business cases, developing project plans, and things like that. If they're alert but not really creative, they could be doing project plan vs. actual tracking, or writing status reports,” Bloom says. “If they're not really up for a mental challenge, they can be returning routine emails, reviewing their spam folder, completing expense reports. If they're basically not sleeping, then they can clean their office, file things, delete old email.”
If managers can give their staff a range of assignments, and teach them this technique, then people can figure out how to plan their day, based on what zone they're in. "IT people can be more efficient if they use zone-based priorities," Bloom says.

Cross-training and speed dating

Keeping up with the pace of change in tech is an ongoing challenge.
Chad Cardenas, chief innovation officer at Trace3, talks about the need to cross-train tech talent in multiple disciplines so companies can better handle shifting business requirements. Cross-training can shake up the status quo and also help with retention of employees who appreciate the chance to learn new skills.

efficiency textchart 1

"Engineers come from different backgrounds, have different skill sets and areas of expertise. Typically, they will get trained up and inserted within that particular wheelhouse of expertise that they already have,” Cardenas says. “That's a challenge for a lot of companies: to break down those silos of engineering prowess and get their engineers cross-trained across multiple disciplines, so they can be more efficient, more powerful, and more valuable to the organization.”
Trace3 offers a training program called ScaleThem that helps clients pinpoint their business challenges and then develops a customized education program, including road maps for each team member.
+ ALSO ON NETWORK WORLD 10 biggest CEO pay raises +
Like many of its offerings, Trace3’s training programs grew out of the firm’s own transformation, over the past several years, from a traditional value-added reseller and systems integrator to a professional services firm with an emphasis on business transformation. As the company morphed, it found it had a surplus of storage engineers and not enough big data talent. Instead of recruiting outside the firm, Trace3 gave its storage gurus the chance to train to become data scientists. The engineers were happy, and the business was growing in the right direction.
"You can get way more out of that investment than you could out of consolidating a server environment or buying a cheaper storage solution," Cardenas says of cross-training technologists. "You're going to have happier engineers who are more engaged, more aligned to the business.”
Another Trace3 offering aims to help IT leaders stay up to date on the latest technology developments. Through its VC briefing program, Trace3 works with venture capital firms to set up a day of meetings in Silicon Valley, tailored for a CIO or CTO. “We curate and customize the entire agenda for the day, full of venture capital companies, entrepreneurs, and founders of early-stage startups,” Cardenas says. “All of the content and the speakers for the session are selected based on the areas of interest and the business needs of our particular client.”
Far too often, there’s little time for researching what’s on the horizon amid the day-to-day requirements of IT, Cardenas says. “It's still shocking to me how, to this day, large IT organizations with thousands of people and a billion-dollar IT budget still don’t have a single person -- let alone a dedicated team -- responsible for researching new technology and then vetting it and integrating it. It blows my mind."

Schedule time for creativity

Cambridge Consultants depends on the creativity of its engineers to solve problems for its clients.
"Clients tell us about a problem they're facing in the marketplace. That might be a competitive threat that they want to respond to, it might be some IP protection that they need to build, or they might be worrying about an expiring patent. We apply technology to solve that problem for them," says David Bradshaw, a director in the Boston office of the UK-based product development and technology consultancy firm.
One way the firm works to keep its employees energized is through its corporate development program, which allows engineers and scientists to pursue their own project ideas.
"Being a consulting company, we sell our hours to our clients. Obviously we carry a surplus of those hours, and we need to find a productive way of using them. What better way than to let the staff be creative on their own ideas? This gives them an outlet to develop in an area that interests them," Bradshaw says. “It leads to better retention, because people are working on things that they're genuinely passionate about. That's the whole idea of the program."

efficiency textchart 2


"That teaches our people to take some corporate responsibility in these things as well,” Bradshaw says. “So we don't just get a crazy array of things that we would never be interested in. We tend to get things that are well thought through and are strategically aligned to what we're trying to do as a business."The parameters aren’t completely open-ended; the firm tries to find some correlation to what the business is trying to achieve, he says.
To ensure that people have time to pursue these side projects, it’s built into the company’s annual planning process. The leadership team reserves 5% to 10% of the firm’s overall engineering hours for these activities, even without knowing the focus of the projects.
Over the years, the program has results in more than 20 corporate spinouts. Most recently, a side project resulted in the creation of Aveillant, which was spun out from Cambridge Consultants in 2011. Aveillant’s holographic radar technology -- which is being used to control radar inference in the wind energy industry – grew out of work a team was doing to prevent auto collisions. An engineer had an idea for applying the technology in a new area and ran with it.
In addition to boosting employee satisfaction, there are other efficiencies as well, Bradshaw says. “These people are training themselves as they're doing this work. They're educating themselves, often going out and finding out about new areas and actually indirectly contributing to the company strategy as these programs are undertaken."
He credits the firm’s corporate culture with making the program work.
“We have a corporate culture of empowering individuals very early on in their careers. We take great people on, we trust them, and we empower them. That gives people the confidence to have these discussions, to believe they can achieve something, to not be afraid to bring their ideas to a manager or somebody who's actually then able to make an investment decision based on that. It's very much an accepted and encouraged part of what we do."
This story, "How to get the most out of your IT talent " was originally published byNetwork World.

Wednesday, December 11, 2013

10 ways to bulletproof your project execution

By  in 10 ThingsDecember 10, 2013, 2:19 PM PST


IT is project-driven -- and if a project goes off track or fails to deliver, the consequences can be dire. These strategies will help ensure a positive outcome. 


10T_pm_iStock_000002674288Small.jpg

Some areas, like accounting, proceed in daily, weekly, monthly, quarterly, and annual cycles of work. But disciplines like IT are highly project oriented. IT's reputation lives and dies with its projects, which makes it essential to bulletproof your projects with strong checkpoints and practices that ensure their success. Here are 10 strategies that can help.

1: Manage by walking around

There's only so much you'll learn about a project's true health by reviewing project reports and memos. If you are the project manager, make it a point to spend time out in the trenches, visiting with staff. You'll pick up a lot about how a project is really going by reading faces and body language. Visiting with people in person at their workstations also keeps communications channels open.

2: Break projects into phases with checkpoints

It's much easier to manage a project -- especially a complex one -- if you break it into phases that can be incrementally tested and deployed. The project team gets to see some early results, as do end users. In addition, a multi-phase project with periodic checkpoints assures you of review time to confirm that the project remains on course and is on its way to delivering the value it's supposed to.

3: Use prototyping as an early-stage project technique

By engaging end users into early project prototypes so they can kick the tires on the project, you save yourself grief in later project stages. That early involvement reduces the risk of users being unpleasantly surprised because the project didn't turn out as they expected. Prototyping also encourages continuous collaboration between end users and project developers.

4: Identify your critical people as well as the project's critical path

Key project contributors may get sick or take maternity/paternity leave or leave for another job altogether, so it's important to identify early in the project who you can ill afford to lose -- and to have backup provisions in place just in case. Most project managers identify the critical path of project tasks that must absolutely be completed, but they fail to do the same thing with their staff.

5: Secure project backing

No matter how sound your project is, if upper and middle management  -- and your immediate user-beneficiaries -- aren't sold on the project, it is likely to fail. Always secure project commitment before starting any work.

6: Use collaborative project management software

There are still companies that manage projects with spreadsheets. Some even use monolithic project management software that resides on a single workstation that a project administrator painstaking updates on a daily basis. But projects are never sequential in their communications or their workflows, so the software tracking projects shouldn't be, either. Today, projects can to be run in a collaborative environment with a project management solution that runs in the cloud. Each project staff member can update his/her task status in real time, giving visibility of current project work to others who are on the project team.

7: Develop a comprehensive QA and test plan... and don't go live until you're ready

Project managers get nervous when deadline begins to approach. Consequently, quality assurance and thorough check-out of projects may get skipped or cut short. This is a mistake. The last thing you want is a public relations nightmare on the first day a project goes live because end users and customers are calling in with their frustrations. If you're the project manager, a scene like this makes it likely that you'll be called in to someone's office as well -- something you definitely want to avoid!

8: Document

It's a temptation to skimp on documentation when you're working a project and deadlines get tight. Resist temptation. If you include and QA the documentation of project modules, callable routines, etc., you make the project handoff easier for your project maintenance team. More than 60% of the average IT department's time is spent on systems maintenance today. Poorly documented projects are one reason why.

9: Conduct a post-project assessment

Even successful projects come with their share of road bumps along the way. Once the project completes, get the project team together to go over what went well and not so well. Then, take what you learn and apply it to the next project. Your project execution will improve.

10: Celebrate!

Project work is hard and relentless. Once a major phase of a project completes -- or the entire project completes -- take time to celebrate the victory with your staff at lunch or dinner or with an office celebration. People need to celebrate their successes so they can be ready for the next project they're going to succeed at.

Friday, July 12, 2013

8 Things Really Successful People Do

Real success takes discipline and methodology. Here are eight things the most successful people are meticulous about getting right.
Business team work building puzzle symbolizing working together

Most people claim to want success. But not everyone is willing to do the hard work and the smart work to get there. Often opportunities present themselves and because people are distracted, they miss them or give up on them before things fully develop.
Truly successful people don't leave much to chance. They are disciplined and focused.  They constantly seek new methods to achieve more, in bigger and faster ways. Listed below are eight different practices that will help you concentrate your efforts on rising above the tide.

1. Make Materialism Irrelevant

Fancy cars and houses are all well and good, but many foolishly focus on the byproducts of success, rather than concentrating on building sustainable success in the first place. Establish a bare minimum for your material needs, and then you can enjoy the benefits of success, debt and stress free.

2. Enhance Knowledge

Success comes faster to those who are open, active learners. The higher up the success ladder you climb, the more complex the systems and opportunities that are presented to you. Absorb all the information you can and if you sense a gap you can't fill, connect with people who have the knowledge you need.

3. Manage Relationship Expectations

People in your life require time. Successful individuals attract folk and so they have to carefully regulate the time they can spend with others. It's hard to limit the time you share and still make people feel important. Make choices about the people who matter to you and determine how you each can get value from your interactions. Then make sure they understand your limitations so they don't take it personally when you can't be present.

4. Practice Emotional Self-Awareness

Not all successful people are calm and nice. In fact, many can be volatile. But most are very aware of their tempers and idiosyncrasies. They know how to use their emotions to get what they want from life and work hard to make sure feelings don't become a detriment. Know yourself and learn how to let your emotions work for you in positive ways.

5. Commit to a Physical Ideal 

Everyone has a vision of their own perfect body. They don't have to be fashion models or athletes to be happy. But physical health is a consideration in their life and it's a big distraction when it gets out of whack. Determine the body you believe is worth working for and set a game plan to achieve and maintain it.

6. Gain Clarity About Spirituality

There are many highly successful people like Richard Branson and Warren Buffettwho don't consider religion to be important or relevant. But they have a clear point of view as to the role spirituality plays in their life. Find your own way to be at one with the universe and be clear and deliberate in how you practice.

7. Adhere to a Code of Ethics  

Really successful people live by rules. They may not be the rules of others, but consistency is important for them to maintain power and stability. Their individual view of how the world works is the basis for how they believe people should be treated and they will defend it until their dying day. Determine your ethical lines and broadcast them loud and clear so people around you know where you stand.

8. Focus on Time Efficiency

Prioritization is a key component of success. You can't reach your pinnacle if you are wasting time on distractions. Integration of activities frees up time for greater achievement. Spend your time on activities that are fun, enlightening and productive and soon you'll have gained hours to reap the benefits of success.
Ultimately, really successful people live their lives by design instead of default, so if you want to be one of them, dedicate time and effort to determining the plan for yourpreferred future and execute that plan in a focused and consistent manner.

Wednesday, April 10, 2013

10 best practices for successful project management


By 

The right mix of planning, monitoring, and controlling can make the difference in completing a project on time, on budget, and with high quality results. These guidelines will help you plan the work and work the plan.

Given the high rate of project failures, you might think that companies would be happy to just have their project finish with some degree of success. That’s not the case. Despite the odds, organizations expect projects to be completed faster, cheaper, and better. The only way that these objectives can be met is through the use of effective project management processes and techniques. This list outlines the major phases of managing a project and discusses key steps for each one.
Note: This article is also available as a PDF download.
PLANNING

1: Plan the work by utilizing a project definition document

There is a tendency for IT infrastructure projects to shortchange the planning process, with an emphasis on jumping right in and beginning the work. This is a mistake. The time spent properly planning the project will result in reduced cost and duration and increased quality over the life of the project. The project definition is the primary deliverable from the planning process and describes all aspects of the project at a high level. Once approved by the customer and relevant stakeholders, it becomes the basis for the work to be performed. For example, in planning an Exchange migration, the project definition should include the following:
  • Project overview: Why is the Exchange migration taking place? What are the business drivers? What are the business benefits?
  • Objectives: What will be accomplished by the migration? What do you hope to achieve?
  • Scope: What features of Exchange will be implemented? Which departments will be converted? What is specifically out of scope?
  • Assumptions and risks: What events are you taking for granted (assumptions), and what events are you concerned about? Will the right hardware and infrastructure be in place? Do you have enough storage and network capacity?
  • Approach: How will the migration project unfold and proceed?
  • Organization: Show the significant roles on the project. Identifying the project manager is easy, but who is the sponsor? It might be the CIO for a project like this. Who is on the project team? Are any of the stakeholders represented?
  • Signature page: Ask the sponsor and key stakeholders to approve this document, signifying that they agree on what is planned.
  • Initial effort, cost, and duration estimates: These should start as best-guess estimates and then be revised, if necessary, when the workplan is completed.
PROJECT WORKPLAN

2: Create a planning horizon

After the project definition has been prepared, the workplan can be created. The workplan provides the step-by-step instructions for constructing project deliverables and managing the project. You should use a prior workplan from a similar project as a model, if one exists. If not, build one the old-fashioned way by utilizing a work-breakdown structure and network diagram.
Create a detailed workplan, including assigning resources and estimating the work as far out as you feel comfortable. This is your planning horizon. Past the planning horizon, lay out the project at a higher level, reflecting the increased level of uncertainty. The planning horizon will move forward as the project progresses. High-level activities that were initially vague need to be defined in more detail as their timeframe gets closer.
PROJECT MANAGEMENT PROCEDURES

3: Define project management procedures up front

The project management procedures outline the resources that will be used to manage the project. This will include sections on how the team will manage issues, scope change, risk, quality, communication, and so on. It is important to be able to manage the project rigorously and proactively and to ensure that the project team and all stakeholders have a common understanding of how the project will be managed. If common procedures have already been established for your organization, utilize them on your project.

4: Manage the workplan and monitor the schedule and budget

Once the project has been planned sufficiently, execution of the work can begin. In theory, since you already have agreement on your project definition and since your workplan and project management procedures are in place, the only challenge is to execute your plans and processes correctly. Of course, no project ever proceeds entirely as it was estimated and planned. The challenge is having the rigor and discipline needed to apply your project management skills correctly and proactively.
  • Review the workplan on a regular basis to determine how you are progressing in terms of schedule and budget. If your project is small, this may need to be weekly. For larger projects, the frequency might be every two weeks.
  • Identify activities that have been completed during the previous time period and update the workplan to show they are finished. Determine whether there are any other activities that should be completed but have not been. After the workplan has been updated, determine whether the project will be completed within the original effort, cost, and duration. If not, determine the critical path and look for ways to accelerate these activities to get you back on track.
  • Monitor the budget. Look at the amount of money your project has actually consumed and determine whether your actual spending is more than originally estimated based on the work that has been completed. If so, be proactive. Either work with the team to determine how the remaining work will be completed to hit your original budget or else raise a risk that you may exceed your allocated budget.

5: Look for warning signs

Look for signs that the project may be in trouble. These could include the following:
  • A small variance in schedule or budget starts to get bigger, especially early in the project. There is a tendency to think you can make it up, but this is a warning. If the tendencies are not corrected quickly, the impact will be unrecoverable.
  • You discover that activities you think have already been completed are still being worked on. For example, users whom you think have been migrated to a new platform are still not.
  • You need to rely on unscheduled overtime to hit the deadlines, especially early in the project.
  • Team morale starts to decline.
  • Deliverable quality or service quality starts to deteriorate. For instance, users start to complain that their converted e-mail folders are not working correctly.
  • Quality-control steps, testing activities, and project management time starts to be cut back from the original schedule. A big project, such as an Exchange migration, can affect everyone in your organization. Don’t cut back on the activities that ensure the work is done correctly.
If these situations occur, raise visibility through risk management, and put together a plan to proactively ensure that the project stays on track. If you cannot successfully manage through the problems, raise an issue.
MANAGING SCOPE

6: Ensure that the sponsor approves scope-change requests

After the basics of managing the schedule, managing scope is the most important activity required to control a project. Many project failures are not caused by problems with estimating or team skill sets but by the project team working on major and minor deliverables that were not part of the original project definition or business requirements. Even if you have good scope-management procedures in place, there are still two major areas of scope-change management that must be understood to be successful: understanding who the customer is and scope creep.
In general, the project sponsor is the person funding the project. For infrastructure projects like an Exchange migration, the sponsor might be the CIO or CFO. Although there is usually just one sponsor, a big project can have many stakeholders, or people who are impacted by the project. Requests for scope changes will most often come from stakeholders — many of whom may be managers in their own right. One manager might want chat services for his or her area. Another might want an exception to the size limits you have placed on mailboxes. It doesn’t matter how important a change is to a stakeholder, they can’t make scope-change decisions, and they can’t give your team the approval to make the change. In proper scope-change management, the sponsor (or a designate) must give the approval, since they are the only ones who can add funding to cover the changes and know if the project impact is acceptable.

7: Guard against scope creep

Most project managers know to invoke scope-change management procedures if they are asked to add a major new function or a major new deliverable to their project. However, sometimes the project manager doesn’t recognize the small scope changes that get added over time. Scope creep is a term used to define a series of small scope changes that are made to the project without scope-change management procedures being used. With scope creep, a series of small changes — none of which appear to affect the project individually — can accumulate and have a significant overall impact on the project. Many projects fail because of scope creep, and the project manager needs to be diligent in guarding against it.
MANAGING RISK

8: Identify risks up front

When the planning work is occurring, the project team should identify all known risks. For each risk, they should also determine the probability that the risk event will occur and the potential impact on the project. Those events identified as high-risk should have specific plans put into place to mitigate them so they do not, in fact, occur. Medium risks should be evaluated to see whether they need to be proactively managed. (Low-level risks may be identified as assumptions. That is, there is potential risk involved, but you are “assuming” that the positive outcome is much more probable.) Some risks are inherent in a complex project that affects every person in the company. Other risks may include not having the right level of expertise, unfamiliarity with the technology, and problems integrating smoothly with existing products or equipment.

9: Continue to assess potential risks throughout the project

Once the project begins, periodically perform an updated risk assessment to determine whether other risks have surfaced that need to be managed.

10: Resolve issues as quickly as possible

Issues are big problems. For instance, in an Exchange migration, the Exchange servers you ordered aren’t ready and configured on time. Or perhaps the Windows forest isn’t set up correctly and needs to be redesigned. The project manager should manage open issues diligently to ensure that they are being resolved. If there is no urgency to resolve the issue or if the issue has been active for some time, it may not really be an issue. It may be a potential problem (risk), or it may be an action item that needs to be resolved at some later point. Real issues, by their nature, must be resolved with a sense of urgency.

Thursday, December 20, 2012

Transitioning into project management without a tech background


Takeaway: Help a TechRepublic member figure out how to transition into a technical project management job without a tech degree.
I recently received an email from a TechRepublic reader regarding applying for a technical project management job even though the candidate didn’t have a lot of technical experience. Below is the reader’s question and my response.

The scenario

“I have 20+ year experience in creative services management for busy in house graphic design teams. We produce promotional materials for off-line and on-line purposes.
Recently, I have started working with the new Digital Director here. I have volunteered to help him build a user experience design for a new web site.  I am interested and motivated about user experiences with technical products and I believe I was built to work in this field.
However, most technical project managers come from a technical background. I am very good at task management - highly resourceful, creative, curious, detail oriented and functional thinker keeping the big picture in mind. My strengths also include intuition, successful staff and resource management. My degree is in Business Administration with an emphasis in Direct Marketing.
There is an opening for a Technical Project Manager job at my company and I am interested in learning more about.
Would you ever consider hiring a person without a technical background? What does someone with my background need to do to get a job managing projects with user experience and design?”

Pursuing the technical PM opportunity

Sometime during my college days, I heard the saying, “You’ll change your career six or seven times in your lifetime.” I’m sure we’ve all heard this saying in one form or another. I consider it useful advice when trying to transition to other job roles that you find interesting even though your background may not be a perfect fit.
Your challenge with this position is demonstrating relevant experience compared to the other people applying for the position. However, in a technical project management position, the hiring manager and you need to assess the amount of technical work required in addition to the project management requirement.
If the candidate has a good understanding of how the technology layers fit together and has past management experience but doesn’t have a technical background, I would still hire that person. I often see this in project management positions for Information Technology jobs. Typically, the Computer Science student is the coder, and the MIS major is the business analyst or systems analyst; either person would make good project managers as long as they can demonstrate an understanding of how the technology fits into the overall plan.
You have more than 20 years of work experience and have gotten an informal education in the digital design and user experience domain. I use experience in the subject matter drive the evaluation rather than the academic credentials. After all, we’re designing websites not engineering pyramids.
Technology keeps changing, so the tools you use today will likely be different in 3-5 years. Your management skills, on the other hand, should improve with experience. By demonstrating past experience and competency performing the technical work, you can position yourself as a strong candidate. Since the job is a project management role, I would highlight the management strengths over the technical competency.
In order to deemphasize the lack of technical experience, I recommend taking an introductory technical course so you’ll have a foundational understanding of the actual application. For instance, it has been 14 years since I coded in Java, yet I took an Android development course to get a better understanding of the work required for creating Android apps. I won’t be developing Android apps any time soon, but I now have a better understanding of the process and the issues developers face when developing apps on mobile platforms, and I am confident that I could manage an Android development project.

Your degree doesn’t determine your entire career

My peers and other executives I know have a mixed bag of degrees and backgrounds. Finance, Math, and even Biology majors have all succeeded in earning senior project management and executive positions despite their lack of a technical IT degree.
Your lengthy career cannot be predetermined by the piece of paper you earned when you were 21 years old; your skills and your collective set of life experiences determine your career. There are no guarantees you’ll get the next position. There may be a better-qualified candidate who has the right mix of technical background, management experience, and the political corporate capital within the company.
I encourage you to apply to the position and consider taking additional technical training to earn enough certifications to balance your experience. Learning doesn’t stop with the initial degree, and hiring managers recognize the importance of a balance between management and technical skills.
What’s your advice for this reader? Please comment your suggestions in the discussion.

Friday, June 15, 2012

TO DO List


Creating A To-Do List


Feel free to use this tip sheet / checklist as you tackle your own ""do-it-yourself"" organizing projects. If you would like to REPRINT or DISTRIBUTEthis information, please click here for reprinting instructions.

6 REASONS TO KEEP A TO-DO LIST
  • can help you take control of your time
  • gives a one-glance look at everything you want to accomplish
  • minimizes mind-clutter by keeping track of odds and ends
  • improves your memory by writing everything down
  • frees up mental "RAM" by emptying your brain of trivial items
  • helps you prioritize your activities
BUILDING A MASTER TO-DO LIST
  • keep a notepad nearby so you can enter items as they occur to you
  • empty all of the to-do's in your head onto a piece of paper
  • don't worry about priority, importance, or time frame for completing
  • this is your "master to-do list"
  • don't try to tackle all the items on this list
  • you will build your "daily to-do list" from your master list
CATEGORIZING AND PRIORITIZING
  • break your master list into meaningful categories by activity
  • home maintenance, work, calls, errands, to buy, etc.
  • break large projects into smaller individual tasks
  • assign a letter code to each item on the list
  • "A" = must do; "B" = should do; "C" = could do
  • prioritize items in each category by letter ("A" then "B" then "C")
DAILY TO-DO LIST
  • limit your daily list to no more than 10 items you hope to complete
  • include no more than 2 large or difficult tasks
  • your daily list includes appointments and commitments to others
  • also include "A" items off of your master list
  • if you have time, fill in the gaps with some "B" and "C" items
  • leave room for urgent items that just pop up
DEVELOPING A NOT-TO-DO LIST
  • not every item on your to-do list has to be done
  • the key to productivity is awareness of how you spend your time
  • what you do, how long it takes, and what benefit you get
  • create a log tracking your activities for a week
  • evaluate the time investment time versus "payoff" for each activity
  • how much benefit or enjoyment are you getting from each activity?
  • keep high-payoff and enjoyable activities on your to-do list
  • ask yourself if low-payoff activities need to be done at all
  • if they do need to be done, do they have to be done by you?
  • if they need to be done by you, could they be simplified?
HOW TO TACKLE YOUR LIST
  • tasks should be completed in order of importance
  • unless they have a specific time frame (like a meeting or class)
  • is this the best possible use of your time at the exact moment?
  • your goal is to complete all of your "A" items first
  • then finish as many "B" and "C" items in the time available
  • be realistic about how much you can accomplish in a day
  • create an agenda for your daily task list
  • schedule times for completing specific activities whenever possible
  • if you didn't complete a task, you had too many items on your list
  • move unfinished items to another day and re-evaluate the priority
MAKING SURE YOUR ACTION ITEMS GET DONE
  • if you procrastinate, create artificial deadlines to finish early
  • know your work style (long stretches or short bursts)
  • understand your high and low energy periods
  • plan your to-do's accordingly
  • make liberal use of memory joggers -- alarms, sticky notes, etc.
OTHER ALTERNATIVES
  • get your family to take on household responsibilities from your list
  • ask a co-worker for assistance with routine business tasks
  • ...and offer to help out the next time that co-worker needs a break!
  • make use of support staff (admin clerks, assistants, etc.)
  • outsource jobs to an independent contractor or freelancer
  • develop a local co-op for sharing time-consuming domestic chores
  • set up an informal chore swap with a neighbor