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.

Posted in General | Tagged , , | Leave a comment

Is being “busy” a good thing?

Ask people from Gemini how they’re doing and the response you’ll most often
hear is “Busy”.  This response begs the question: Are we really busier than
other observatories, or do we just like to think we are?  I suspect it’s a
little bit of both.  (I’m picking on Gemini and exaggerating a bit here,
but the same thoughts apply to many workplaces, I’m sure.)

 

http://inspacesbetween.com/insights-inspiration/declaring-war-on-the-busy-epidemic/

http://inspacesbetween.com/insights-inspiration/declaring-war-on-the-busy-epidemic/

It’s true, people are busy, but it’s more than that. Being busy is part of
our culture. There’s an advantage to that. If you’re busy, you’re working
hard and progressing your company.  On the other hand, if you’re busy, you don’t
have time for everything on your plate; you’re more free to select items
you want to do and discard the rest.  If you’re busy, you don’t have to
take the time to think about long term goals and strategies; you’ve got
plenty on your plate that’s due now.  If you’re busy, you don’t have to
take the time to communicate and explain your plans; people who need to
know will know; the others don’t need to be distracted.

Clearly there’s a tactical advantage to having a culture of being busy.
Yet, as I hope is obvious, there is a strategic price to pay for this cultural state
as well.  Some tasks don’t get done and there can be little control of
which ones do and which ones don’t. Tasks that seem important now often see
more activity than tasks that might make the observatory a better place in
the future.  Sometimes easy tasks that can be done now get worked on before
harder tasks that have a later payoff.  People stop informing others about
what they are doing and there is therefore less alignment and buy-in for
some activities than there might otherwise be.   People who facilitate
communication and joint problem solving through significant social
interactions  can find themselves under-appreciated and often leave to find
a place where they can work to bring people together as a team.

There is clearly a cultural reason for Gemini’s busyness, but is there
another cause? Are we simply doing more with fewer people than are other
observatories?  Gemini’s staff size is larger than those of other
observatories by some measures, comparable, by others. Our queue system and
need to support two facilities on two significantly different locations
might justify some increase in staffing compared to other similar
facilities.  As a result of the UK pullout from Gemini, we are reducing our
staff size and this effort will certainly mean some people are asked to do
additional work while our transition to a leaner operating state is
underway.  So, there may be some truth to the idea that our staff is
imply too small, but I want to consider what alternative explanations might play a role as well.

It might also be that Gemini staff are simply doing (or attempting to do)
too much.  Comparing Gemini to other facilities, though, it’s not obvious
that we are doing a whole lot more than anyone else is. Yes, there’s the
queue and our dual-site support need, but this effort is pretty much
accounted for in our staffing levels. (Although it is possible we aren’t
staffing as much as we need to do in these areas.)  If we assume, though,
that we’re not staffed too small and we’re not doing more than other
observatories, is there another possible non-cultural cause for our
busyness?

One key difference between Gemini and the other 8-10m telescopes is its
ownership.  While the users of the other telescopes are largely dependent
on that telescope, Gemini’s communities either have access access to other
comparable facilities or a small enough percentage of Gemini’s time that
they don’t feel they own the observatory.  With no direct sense of
ownership of Gemini, the external Gemini community is less involved with
the observatory than they might otherwise be.  The fact that our governance
is complicated and areas of relative responsibility can be poorly defined,
makes it even more difficult for Gemini users to know how to contribute to
the observatory, even if they wanted to.

Gemini’s procurement structure also inhibits our community from feeling
ownership of Gemini.  We end up partnering less with our community members
than we do working as a customer of their services and products.  As a
result, our development efforts require more internal resources than they
might if we had more in-kind support form our community.
New instrumentation for Subaru and Keck, for example, are often initiated
by the universities that use the telescopes – not normally the case for
Gemini.  Instrument teams for the other telescopes often support instruments
in operation and write reduction software for end users – all things Gemini
usually does itself.

The cultural aspect of Gemini’s busyness has a good side – a dedication to
the observatory and a willingness to work hard. If we could keep that
aspect of our culture and add long term strategy formation, efficiency
improvements, and community, communication, partnership, and engagement,
then you have a pretty exciting observatory.

In addition, to better leverage our strong community, the next partnership agreement
could be structured with in-kind contributions and direct in-kind
community investment in Gemini, rather than cash contributions and a Gemini
obligation to distribute development money back to the partners in the same
percentage as it was contributed, as we do now.  This approach would help
build a sense of community ownership of Gemini and will allow more work to
get done for Gemini, but not directly by Gemini employees. This approach
will also engage our community more fully with our staff and encourage more
communication and strategic thinking.  Gemini can lead its class, but we have to not only modify our culture of busyness, but find better ways to leverage the utility of our community.

Posted in General | Tagged , , | 3 Comments

Resource Management: Focus on the workers, not the managers.

Inspired by the Norm Smith talk I recently heard (see previous post), I purchased his book Got Progress? and highly recommend it. I now have words to describe some of the unease I’ve been feeling about my workplace’s current project management and resource allocation approaches.

The brightest light bulb went off when Norm bold-faced (and I’m paraphrasing): Build project management structures for the people doing the work, not management. In particular, Norm revealed that he rarely found a resource-loaded project plan very useful and integrated master plans even less so. Why? Part of the reason, is these things are usually done for management, not for team members.

Where I work, we spent a lot of time developing a system to let management know if we have enough resources to do the projects we want to do. We’ve evolved from rough estimates to complicated spreadsheets to an online project task and resource tracking tool to a interwoven combination of all these tools. We have reports that go from project managers to a resource review committee to upper management. In short, we have a very complicated system that ensures resource estimates and allocations are properly conveyed from project mangers to upper management. The problem is, the average employee would agree with Norm Smith in saying it’s great the management knows (or at least, thinks they know) where resources are allocated, but wouldn’t it be nice if the project team members (also called Project Implementation Specialists, in PMBOK speak, I just recently discovered) also knew where they were allocated?

We’ve built a very details system of resource tracking mechanisms for management, not for project members. We have tools that tell management that every staff member is fully allocated to the necessary projects, yet when I talked to several random project members recently, they admitted to not knowing everything they are supposed to be doing. Clearly, the complex system derived to let management know that everyone is properly allocated to the projects to which they should be allocated, is failing to make the resources themselves aware of what’s expected of them.

Crazy idea: develop the system so that project members each have a clear understanding of what their tasks are and let over-allocated resources (conflicts) rise from below. If employee-X knows what tasks are expected of him and doesn’t have a problem getting everything done on time, what more does management need? Similarly, if employee-Y realizes she can’t do all of her project work on the schedule required, she can raise her concern upstream without complicated structures and calculations put in place to detail her exact level of loading.

Our goal is to get the work done. It does no good for management to look at an integrated master plan and see that everyone is assigned the right percentage of time for the right tasks if the employees themselves don’t know what’s expected of them. Build a system that makes it clear what is expected of them (and that system would ideally be tailored to the individual, team, and particular project), and you have a system that has buy-in, accountability, and self-policing. If the work is getting done and conflicts are identified and highlighted by those doing the work, management can focus on only the conflicts that arise, and the project implementation specialists can concentrate on getting their projects implemented!


Speaking of project implementation specialists, Scot found Norm Smith’s book so useful partially because it clearly represented real-world experience with project management. Textbook project management, like the PMBOK, for example, provides a fine framework for project management, but needs to be implemented while taking account of real project complexities and not treating each project as if were the ideal project. Like the frictionless pulley, Scot suspects the idealized PMBOK project doesn’t exist.

Posted in General | Tagged , , | Leave a comment

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.
Posted in General | Tagged , , | Leave a comment

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.

Posted in General | Tagged , , | Leave a comment

On systems, processes, and paperwork

Lately, I’ve come across several proposed new systems, processes, and forms —  all developed to address an assumed real, but unstated need.  In most cases, I could see a useful purpose for the new system/process/form,  but it usually wasn’t provided to me explicitly.  I didn’t know if my interpretation of what this new proposal was all about was shared by those directing it so I often feared I would be wasting my time by doing something that wasn’t what was actually wanted.

Developing a common framework and tools for management tasks makes sense, but there must be a system behind them, else you just end up creating a bureaucracy instead of an effective, efficient system.  I see several things to address before implementing a new system, process, or form:

  1.  What is the purpose/goal? What problem are you trying to solve?
  2. Who is your audience?
  3. What are the requirements needed to fulfill your objectives within your target audience?
  4. What are the implementation costs?
  5. What are the costs of non-implementation?
  6. Given all the above, is implementation the right approach?

There’s nothing terribly new here, but the items above make a good checklist to go through before starting a new formal process.  If you don’t address the first three points, you may end up spending a lot of time doing something which propels you no further down the road.  In addition, if you don’t evaluate the costs of what you’re proposing against the current incurred costs in light of your available resources, you risk spending too much time on something that is ultimately not going to improve your situation enough to be worth it.

Large projects need a fairly broad framework in which to operate.  They also, typically, staff a project office sufficiently to help produce and support this framework.  While smaller projects can also benefit from this same framework, typically the cost of doing so is prohibitively high.  So, smaller projects must think carefully about what it can do, what it can’t afford not to do, and ignore the things it can afford to not do.  Going through a similar checklist as above ought to help decide into which category a proposed new system belongs.  (Actually, I’m sure this same approach works for large projects as well — we are all resource-starved these days.)



Speaking of checklists, Scot found the book “The Checklist Manifesto” by Atul Gawande a very good read and a great strategy for helping to ensure routine tasks are done correctly every time. Packing for trips, as an example, got immensely easier once checklists got involved.

Posted in General | Tagged , , | Leave a comment

Musings on the future of Astronomy

The future of astronomy seems clear to me right now. It goes through ESO.

That’s not particularly bad, especially if you’re an ESO member, but if you’re not, things may be a little less good. With the addition of Brazil, ESO has begun its expansion beyond Europe and it’s no secret that several other non-European countries are currently considering joining ESO. ESO stands to gain even more attention if one of the competing Giant Segmented Mirror Telescopes (GSMT: TMT/GMT) do not take off or appear to get the critical national support they need to attract and hold new funding partners. The world’s astronomers may have no choice – join ESO or stay out of the large telescope game.

Now, I have nothing against doing science with “small” (< 8m) telescopes. There is a lot of attractive and compelling science to be done there. The “smaller” telescopes offer more opportunities to innovate by using new observing techniques and equipment, having access to larger amounts of telescope time, and affording the opportunities for high-risk, high-gain projects that couldn’t be assigned time at the larger telescopes. But if you want a balanced national program, you are going to want access to the world’s largest telescopes, as well.

In the thirty meter telescope era, funding and general support for the 8-10m telescopes will decrease. No problem for ESO – it has a full house of telescope of different apertures and functions, working in conjunction to support one another and produce a well-balanced suite of capabilities for its user community. It is more of a problem, however, if you’re a single (or even dual) 8m telescope owner like Gemini, Subaru, or Keck, for example. Mauna Kea astronomy is some of the best in the world, and yet, without a GSMT for its community, and in the face of shrinking budgets as its telescope owners either divest themselves from the Mauna Kea telescopes to invest in a GSMT or ESO or simply to reduce their commitment to astronomy, Mauna Kea telescopes will decrease in relevance. ESO is great, but for the good of astronomy, we can’t let Mauna Kea, we can’t let non-ESO astronomy, fade away.

One possible solution has been discussed for ages, but never fully endorsed or implemented. It is starting, however to reappear in several different forms for different, but related reasons. We must somehow unite the telescopes on Mauna Kea into something greater than the sum of the individual observatories.  There is a VLT right now on Mauna Kea, but we just don’t operate it as such. Actually, when you consider the unique strengths of even just the 8-10m telescope on Mauna Kea, we have a potential uber-VLT in our midst. Add community access to Gemini South and you have a facility which could conceivably span both northern and southern hemispheres – a very worthy competitor to the VLT.

Establishing some sort of Mauna Kea Federation has several advantages: 1) it would allow each observatory to concentrate on what it does best, reducing the costs incurred in trying to provide each independent community access to the entire spectrum of wavelength and resolution coverage on the sky, 2) it would allow each facility to offer a capability in its strong suit that is currently beyond anything it can currently afford to do, 3) it would form a natural community to not only fund, but properly feed and support, a non-ESO GSMT, and 4) through shared resources, it would provide each community with better access to tools and facilities than any community currently has.

In the inevitable funding cuts that will certainly come to the current Mauna Kea telescopes, the disparate Mauna Kea communities must join together if they are going to continue to have access to the level of infrastructure they are used to. It is unlikely that any existing Mauna Kea observatory will be able to offer the same range of wavelength and resolution in cutting edge instrumentation with the high levels of support that it currently does. Downgrade your capabilities or unite. There will be no other choice.

So, given all this, how do we unite the current Mauna Kea telescopes? I don’t at all claim to know the detailed answer to that one, but I think the path includes the word federation. We must find a way to allow each observatory to retain its current identity and functional systems while allowing each observatory to develop capabilities that both play to its own strong suit and are attractive not only to its own community of users, but to the communities from the other telescopes as well. I don’t think this task is all that hard (the large Mauna Kea telescopes have some natural complements to each other already), but it will take a change in mindset to implement. In the meantime, I think each facility ought to be increasing its strengths and planning for a future where these strengths are traded for high-level capabilities at the other facilities. Playing to our strengths is a good strategy even in the absence of a Mauna Kea Federation. As each facility further develops its strengths, though, it will find that not only is its community enjoying the new benefits, but other communities will start looking for ways to get access themselves. By making our facilities the best at what we can each do best, we will start driving the demand for some sort of federation at both ends: our own communities will start wanting access to capabilities in short supply at our facilities and other communities will start wanting our unique capabilities to complement theirs as well. If we do this right, need and desire from both sides will help us find a way form our more perfect union.

Realtime demand is a more effective motivator for change than is forward thinking and long term planning, however accurate and omniscient it may be.


Scot has nothing against ESO, and actually thinks they have a great facility and approach to fulfilling their communities’ needs, but for the good of astronomy, he thinks a little friendly competition and rivalry is a good thing. He’s pretty sure the ESO community would say the same thing, if asked.

Posted in General | Tagged , , | Leave a comment

I am can be powerful!

The other day, someone came into my office with a bad idea for a project of mine. I regularly get bad ideas from this person, so I naturally have just set myself to resisting whatever this person (let’s say a “him”) says and hoping he’ll go away and leave me alone so I can do what I know is best anyhow. Sometimes, though, this person wins and I end up begrudgingly doing what he suggests, even though, I “know” it’s not the best thing to do.  Either way, I usually fight his ideas.  Because mine are better.

Or so I thought.

On this particular occasion, I lost myself and somehow decided to listen to this person and find out why he thought this idea was good, even though my initial reaction was that my own plan was better. I decided this time to really hear what he had to say, though, and actually discovered there was a good idea here that I had missed. I still didn’t like the implementation he put on his idea, but there was a good idea behind it all, a good idea I was about to dismiss entirely. After a few more moments of discussion, we actually arrived at a new plan, that was better than either one of our original ideas. He walked away happy and I had a better solution than I would have otherwise.

By being willing to listen, by exploring this seemingly bad idea for just a moment before dismissing it, by looking for the idea’s motivation and treating this person as a real person with skills and motivations I made someone who I might have considered a time sink into someone who can actually help me do my job.

Now that’s power we can all use and learn!



While Scot acknowledges this story is slightly fictional, and really only slightly, he writes it as a good reminder to maintain an open approach to ideas and people.

Posted in General | Leave a comment