Tag: Management

  • Breaking projects into tasks

    I was been feeling a bit unmotivated at work a while back until I realized one reason why. I took (yet another) look at my task list and found most of the remaining items were not tasks, but projects. They were projects that would take multiple hours to complete and in many cases weren’t clearly defined as to their final results. What were these projects supposed to produce? How would I know when they were done? How would I start them?  No wonder I didn’t feel motivated. People don’t do projects; they do tasks. When I looked at this task list I saw vague, undefined projects that had no defined end and no defined place to start. They represented hours of work when I rarely have consecutive hours I can spend in one place to work on one project.

    So, I picked an item of my list and asked myself what I needed to do to start on it. In this particular case, the answer was to locate an old version of a similar document I had to write, take a look at it, and decide how I wanted to change it for the new document I had to write this time.

    A colleague and I regularly teach this trick in a task management class we lead, and it’s standard course in any Getting Things Done like approach: always start and stop a project by noting your next task.  Doing so always gives you a concrete place to start when you pick the project up.   I shouldn’t have had to remind myself to do this, but at least I’m glad I eventually remembered.  A good reminder for myself, but also good to keep in mind when people you work with are not making the progress you expect. Maybe they don’t know where they are headed or maybe they don’t know how to get started.  There are both easy things to fix once you are aware of what to look for.

  • Who are you?

    Who are you, if not your job or profession?  I asked myself this question recently, and didn’t have an immediate answer.  It’s easy to say I am an astronomer, or I am my job title, but what am I besides my job?  What are you?

    I’m sure for some people, this is an easy question to answer, but for others like me (an enneagram 3) who tend to identify themselves with what they do, it’s not as easy.  Sure, I am a son, husband, father, brother, uncle, etc., but these don’t define me.  They don’t make me me – with the possible technical exception of being a son, of course. 🙂

    I am an adventurer.  Yes, but no. I like discovering new things and I am usually up for an adventure, but I don’t really live for it.  What else could I be?

    I am an expert.  No that’s both too arrogant and inaccurate. I have too many interests to really be an expert in any/many of them and although I want to learn how things work, I don’t feel I have to be an expert in them, so that’s not right.

    I am an observer. There’s some truth in that, and not just as an astronomer, but it sounds too passive. I like watching things and noting how things work, but I don’t want to just watch things happen, so I need a more active description.

    I an optimist. That’s close, but I don’t go through life looking for things to be optimistic about.  I believe we can often make events good simply by choosing them to be so while other times, we can extract good from an otherwise bad event by studying it and working to do so.  So, optimism is more of a tactic than a strategy for me.

    I am an explorer. OK, that’s sounding better.  It describes my interest in science and astronomy and includes key applicable traits of being an adventurer and an observer.  I explore to understand how things (including organizations and people) work. I explore to learn how to make them work better; how to use them to do other things; and sometimes simply just to understand them.  In the process of exploration, I’ll often take something I know and look at it from a different angle or do it in a different way. All this fits with being an explorer; it is,  at least, the best I’ve come up with so far.

    Beyond my attempts to peel back my own onion layers, what’s my point here? That each of us is more than our jobs and our professions and that by understanding both ourselves and our colleagues better, by understanding who we are besides what we do, we can better work with each other to create better environments for people to live and work to their potential.

    So, who are you? And who are your colleagues? Are you working to help give them what they need to be themselves? Are you creating an environment where each of you can get the most return out of being who you are?  Do your colleagues know who you are so they can do the same for you?


    Scot’s been suffering from jetlag recently and this post arose as a result. He hopes, however, it still makes some sense and he wishes you all, whoever you are, a happy holiday and a great 2015.

  • Give yourself time to think

    Why is it we schedule time for meetings, but not time for thinking?

    Take a look at your calendar. If it’s like mine used to be, it’s a series of scheduled meetings with some blank space in between for more meetings to eventually be scheduled.  As I said in a previous post, meetings are (or at least should be) real work, but there is some work you sometimes have to do by yourself.  Like thinking, for one.  We scheduled time for meetings, we sometimes schedule time for doing, but we rarely schedule time for thinking.

    As a result, I now look at my calendar a little bit differently. Instead of viewing it as a list of meetings and times available for meetings not yet scheduled, I now directly schedule in times for doing and thinking along with times for meetings.  I regularly block off 1.5 days a week for working – with no meetings. I also schedule an hour a day for thinking.  This time sometimes ends up being used for doing, but I do often use it for thinking.  I try to use the time to think about how I might apply some business world technique or strategy to astronomy.  I think about our observatory’s strategic needs and how we might better address and fulfill them.  I think about our competitive environment and how we might better connect with our stakeholders.  More often than not, these hours result in some obvious, quick action items that result in making progress on long term objectives that would not normally see the light of day in a calendar filled with meetings and slots for potential meetings.

    I still don’t have enough time for doing as I would like, but these brief thinking sessions help my doing time be more productive and they help me better formulate tasks I end up delegating, helping them both start off on the right foot and ultimately contribute to a larger strategic goal.

  • Some thoughts about commitments

    No, this Blog is not dead. I think about it often; I just don’t have as much time as before to update it. I started taking some remote classes (what was I thinking?) and they are pretty much devouring every spare second I have, so this blog, along with most of the rest of my life, suffers.

    I am learning lots of neat new things that apply to astronomy management, though, and I am anxious to get them up here eventually. One concept I am pondering now is the use of hard commitments in astronomy. In the real world, a hard commitment is used to signal your intentions to competitors. It is designed to get them to act on your intentions and as a result, it is characterized by three things: visibility, understandability and irreversibility. For example, if you make a press release saying you are going to expand production, that is visible and understandable, but fairly easily reversed. On the other hand, if you invite the press to witness the unveiling of your new $26M factory, that adds a level of irreversibility to your signalled intention. Your competitors are going to have take your increased capacity into account when they plan their strategies.

    There are lots of applications of this concept in astronomy management. For example, if a manager asks you to join a new working group to address issue X, or join the team of project Y, you may be wondering if it will be worth your while to do so. Will your eventual solution to issue X ever get listened to and implemented? Will project Y ever really happen? What if, instead, that manager told you that project Z was killed so that project Y could get have the resources it needed to succeed, or that the chair of the new working group is a new employee whose full time duty is to solve issues like this? Wouldn’t you be a little more convinced that your time would be well-spent? Showing real, hard to reverse signs of commitment to a project helps others commit to it as well.

    You can apply this concept as well to claim scientific capability ground in telescope operations and instrumentation. I still think we should be cooperating more with each other, in general, but there are also appropriate occasions to clearly signal your intentions if you want to make something actually happen on a desired timescale. A hard commitment is one way to do so.

    Stick around, and I may some day write about how a hard commitment helped make a dream happen at our observatory.

  • Additional Random Bits from the NASA PM Challenge, 2012

    The annual NASA PM Challenge is a really good meeting. The speakers are generally excellent and the material covers a wide range from project management fundamentals to the latest great and innovative management ideas. The ratio of outstanding talks to duds is excellent at this conference. Following up on my last post about Norm Smith’s talk at this meeting, here are some additional random ideas, lessons, and thoughts I noted from various talks at the conference:

    • Be wary of SPI: it does not care if the work performed was on critical path or non-critical path items. Your project may be more or less on track than SPI indicates.
    • For typical projects, CPI does not change significantly after 20-30% of project completion. If the CPI is not good at that point, significant intervention is likely needed to correct it.
    • Good PM risk reduction technique: ask “If I gave you some $, what risks could you reduce for how much?”
    • Listen to learn.
    • Think “I get to” vs. “I have to”.
    • Contracts need to acknowledge and provide for iterative and collaborative risk management.
    • Contracts should support and provide for strategic as well as tactical collaboration.
    • How many technical innovations from the past 20 years do you use daily? How many management innovations from the past 20 years do you use daily?
    • Sometimes you have to cast away past successes to reach new ones.
    • No one comes to work wanting to do a bad job.
    • Adapt to your team, not v/v.
    • Starting a new online platform? Seed it with content before going live. People won’t come back if there’s no point the first (few) visit(s).
    • Take your job seriously; don’t take yourself seriously.
  • Managing Cost, Schedule, and Scope is not enough.

    Project Management 101 teaches the need to actively, and simultaneously, monitor and manage a project’s cost, schedule, and scope. Project Management 102 might add risk management to the list as well. These ideas have become fundamental tenets of project management and have been around for decades, yet projects still fail. Are project managers simply not learning these lessons and not actively managing this crucial project management trinity? Or, perhaps, is there something more that’s needed?

    I certainly agree that a project must manage its cost, schedule and scope. I’ve even written about the importance of doing so, but this alone, as countless delayed, over-budget, and failed project have told us, is not enough to ensure project success. A project must first be addressing the right issue. Is the result of the project what is needed? A project also needs a project sponsor who can provide support when needed and work internal and external stakeholders to develop a consensus for and enthusiasm about the project. Additionally, a project needs overall stakeholder involvement and buy-in. And finally, a project needs good change management. Change will happen; it’s how it is handled that can make or break a project. Without properly addressing these items – project purpose, sponsor and stakeholder involvement, and change management – even proper managing of cost, schedule, scope and risk will likely still result in a failed project.

    Norm Smith, in a recent talk I attended, (you can read more about Norm Smith and his ideas at his website: http://www.smithops.com/Training.php; I definitely recommend watching Norm’s brief video via that link), broke this list down (and improved it) as:


    • Situational Awareness
    • Enfranchisement
    • Boundary Maintenance

    Situational Awareness is understanding where you are in the project, where you started, and where you are going. Schedules and project plans are often the tool used to create this awareness, but they don’t always work for that purpose and they are often used more as a means to themselves, and not as a tool designed solely for situational awareness. Norm stressed the importance of using a schedule to the detail needed to provide the right amount of situational awareness. You don’t always need each work package broken into half-day tasks to successfully manage a project and maintain situational awareness.

    Enfranchisement is fairly simple – getting your team and stakeholders (including the project sponsor, which I had separated out, above) united in the project mission. This task is crucial if you are to efficiently deliver the right products and overcome unexpected surprises thrown at you along the way.

    Boundary maintenance is akin to scope management and change control. It is making sure the project does what it is supposed to do, not more, not less. It is also responding appropriately to the change which is inevitable for most projects.

    In this new light, managing cost (ex., Earned Value Accounting), schedule (ex. Work Breakdown Structures, Microsoft Project), and scope are simply tools used to create the situational awareness and boundary maintenance that are the real core components necessary for a successful project. Don’t let these tools control the project. They are not the essential tools for a successful project; they are simply tools, and not the only ones available at that, that may help you create the real elements needed for project success.



    If you’re interested in project management, especially as it pertains to large projects, Scot highly recommends the annual NASA Project Management Challenge meetings. Some of the best talks he’s ever heard have been at these meetings.

  • Real vs. fake work: What are emails, meetings, etc.?

    A couple years back, a group of us at work put together a series of classes designed to help people better communicate and manage their tasks more efficiently.  We present them in a sequence we think makes logical sense: Email Management, Task Management, Setting Deadlines and Following-up, and Better Meetings.  There is a common refrain heard during our classes that the material is all fine and good, but people just don’t have time to practice and do all the techniques we discuss.  People who try to do these things complain that doing so leaves them no time to get any real work done.  They say this as if being busy were excuse enough to avoid these responsibilities, as if responding to emails, managing task priorities, following up on task requests, and properly leading and preparing for meetings were optional things that can be skipped when they are busy.  I no longer wonder so many people think sending emails (if no one responds to them), setting priorities (if no one pays attention to them), doing work requested from others (if no one ever checks in to see how things are going), and attending meetings (if no one ever prepares for them) are a waste of time.

    While many of us would like to spend all our time doing only that part of our work that we enjoy, whether it be writing software, designing or building new instruments, conducting research, or whatever,  few people have that luxury either in their organization or perhaps ever in their own work lives.  So, let me say something very unpopular: answering email is real work.  Making sure you are working on the most important thing to be working on in any given moment is real work.  Following up on tasks you depend on that others are supposed to be doing is real work.  Attending meetings is real work.  These things are not fake work. They are not pointless tasks that don’t further your organization’s objectives (well, at least they shouldn’t be – more on that later).  They are part of the necessary ingredients for running and working within an organization.

    Now, all that being said, I do admit that not all emails contain useful information or necessary requests for action, not all tasks on your todo list are of equal importance,  and some meetings seem to have no practical purpose, but these examples should be the exception, not the rule.  What most treatises on managing your email and tasks and running better meetings leave out, for example, is the first step: eliminate as many unnecessary emails, tasks. and meetings as possible. Try sending less email; you’ll probably get less in return.  Pick up the phone if there’s a complicated issue involved rather than sending 12 rounds of email.  Call a meeting if many people need to be consulted on a complex issue.   Accept new tasks only if you can make the time to devote to them.  If a meeting isn’t making a decision, why are you having it?

    Eliminate extraneous emails and meetings, but do process the rest fully. This is real work.  If you have too many tasks on your plate to manage; too many people to follow-up with, too many meetings to attend, then you probably aren’t getting everything done and you might as well select which tasks aren’t going to get done by purposefully eliminating them from your plate rather than letting random fate dictate what tasks you do and which you don’t. When you’ve prepared yourself a plate of tasks appropriate to your available time, manage those tasks properly; follow-up with others needed to help you complete your tasks and projects. This is necessary work.  This is real work.

    Recently an attendee from one of our classes asked me if David Allen had any quantitative evidence that regularly emptying your inbox actually made you a better performer at work.  Although he had a slightly different point in mind, I responded, in part, as follows:

    No, I don’t believe David Allen has any quantitative evidence that emptying your inbox is a good thing. I’ve never seen any, at least.  I also don’t think he needs any. Do we need numerical evidence to show that listening to our phone messages is a good thing? That writing down action items assigned to us at a project meeting is a good thing?   To me, emptying my inbox is about understanding my tasks and workload; I can then decide, by choice, how to handle each task (do, delegate, delete, file, re-negotiate, etc.) and be confident I am not letting some critical request on my time go unnoticed, lost in my inbox.

    The email inbox represents a task list. Some tasks can be dealt with quickly while others take more time. But if we don’t go through that task list and make decisions about which tasks to do and which not to do, we are letting chance dictate which tasks get done and which not, simply depending on which emails we happen to look at. (We also make ourselves uneasy, wondering what we’re missing or forgetting about that’s contained in that inbox.)  Emptying our inboxes is not about completing all the tasks that the emails represent, but about getting the tasks out of our inboxes (it’s called an inbox for a reason) and into our task management systems where we can decide when to schedule/do the work. David Allen’s point is that it is just as necessary to process our email inboxes as it is to answer our phones, get our mail, respond when someone knocks on our doors, etc.

    What David Allen doesn’t address, is how to minimize the number of potential tasks that come to us via our email inboxes.  That is something we tried to include in our classes, though, since we believe it’s a key part of the solution to getting our inboxes under control.

    So, if you don’t have time to handle your email properly, manage your tasks and your requests of others sufficiently, attend and lead productive meetings, then the first step is to eliminate clutter from your work life.  Cut down on the emails you send, filter emails you know don’t need attention right away, unsubscribe to some mailing lists.  Delegate, re-negotiate or reject tasks you aren’t going to get done.  Eliminate unnecessary meetings from your schedule.   But once you do these things, your work isn’t done unless you manage your emails and tasks, check in with those working on tasks for you, and come prepared to make meetings productive.   These tasks are necessary. They are real work.  They may not be the most glorious of tasks on your plate, but if you don’t do them, the rest of your real work will likely suffer.


    Unfortunately, Scot isn’t perfect, either, in making sure all the necessary non-“real” work gets done in his life, but he has found that when he does do it, things go more smoothly and this has been pretty good motivation to make the time to try to do these things right.

  • Superficial pleasantries vs. honest relationship building

    In my last post, I discussed some thoughts from reading Conger, Lawler, and Finegold’s Corporate Boards book. Here is something else that caught my eye in that book that has near universal applicability -not just to corporate (or observatory) boards.

    In a section of the book on how boards can/should review themselves, the authors write about why most boards don’t end up reviewing themselves in any meaningful way:

    There was a concern it might cause disharmony in the group. It was that primitive notion of what creates more effective teams. ‘Effective’ teams in this case, are where you skirt issues of difficulty, or personal differences. It’s more like ‘We want to be able to have a drink together and like each other’ as opposed to ‘If we confront ourselves on real issues, we’ll deepen the relationship.’

    There’s not much more that needs to be said after the authors’ summary.  Too often people, managers, team leaders, team members, employees, fail to raise an issue for fear of being confrontational, of being thought of as not nice.  There’s a common (mis)perception that if we confront people, if we speak up when something is wrong, then we are not being nice; we are not being good colleagues; we are poisoning the congenial atmosphere. This attitude is, of course, silly, as the above passage points out.  By not confronting the real issue, by not making these tough decisions, we may establish a superficial pleasantness, but we don’t ever dig any deeper and build real understanding that leads everyone to peak performance and a more satisfying environment.

    Confronting people does not make you tough or mean. You can confront someone in a mean, objectifying way, or you can confront people in a helpful, supportive, personal way.  We’ve all heard of stories (usually told of great managers) who fired someone only to have them return some time later and be quite successful. Were these people fired in a mean-spirited, impersonal way? Probably not. They were probably fired with sincerity, reflecting on the fact that their employment in their current role was not only not working, but was of little benefit to either party.  They were fired with honesty.   They thus created the opportunity to learn from life’s problems.  Firing, reviewing, confronting someone with malice or dishonesty at heart does not provide a foundation from which anything greater can develop.

    Same behavior, different attitude. You can “be mean” and confront someone or you can “be nice” and confront someone.  Honest confrontation meant to improve the relationship, the teamwork, and the results is not only healthy, but necessary for high performance.   Skirting around the interpersonal issues gives you two people who can go drink together, but who won’t ever build a bond and a team that will lead to greatness.



    While Scot hopes he will never be fired with either good or bad intentions, he does look forward to opportunities to develop an honest, deeper understanding with his colleagues, although seizing these moments is still not always as easy as he would like.