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

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.

Posted in General | Tagged , , | Leave a comment

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.

Posted in General | Tagged , , , | Leave a comment

Balancing Two Boards

Gemini has two Boards – the Gemini Board from the international partnership agreement and the AURA Board. It’s actually a bit (well, OK a lot) more complicated than this. The National Science Foundation (NSF) is Gemini’s Executive Agency. They collect and distribute the funds for Gemini from the Gemini partnership. They also provide the funds for the US part of Gemini. AURA is our Managing Organization and is basically responsible for the management of Gemini. They have their own board and a specific oversight committee for Gemini, the AOC-G. The Gemini Board is basically our governing body, being the representatives of the partner countries to Gemini’s operating board. If each of these agencies, boards, and committees wants a review twice a year, Gemini would (and quite nearly does) end up with a major review a month. This would be bad enough, but as you can imagine, with so many organizations, boards and oversight committees, it can get a little confusing figuring out who is responsible for what and to whom. The lines of control and authority are blurred and complicated. The Gemini Board sets Gemini’s direction, yet Gemini’s Director takes home a salary provided through AURA. The reviews from the different groups in the observatory’s governance structure often end up commenting on the same aspects of the observatory while leaving other aspects untouched. In some areas, everyone wants their piece of the action, to have their say, while other aspects escape without much scrutiny at all. Overall, it’s a recipe for confusion and disorder.

The Gemini Partnership Agreement specifies the general roles of the Gemini Board, the Executive Agency, and the Management Organization. but of course not those of each of their boards and oversight/review committees. So, even if everyone read and understood the Partnership Agreement, there would still likely be confusion. The Partnership Agreement and Management Organization’s contract will be up for renewal soon (~2015) so we have an opportunity in a few years to simplify this whole structure and come up with an organization that has clearer and cleaner lines of authority and responsibility. In the meantime, though, we still have to make things work a little better than they do now. The unclear lines of communication and authority are hindering us from becoming a true high performance organization with a single team able to focus on a common mission.

Balancing Gemini's Boards takes some care and thought, but should not be too difficult if can agree on a clear division of roles and responsibilities.

In their book, Corporate Boards: New Strategies for Adding Value at the Top, authors Conger, Lawler, and Finegold define the primary roles of the corporate board as follows:

1) giving strategic direction and advice
2) overseeing strategy implementation and performance
3) developing and evaluating the CEO
4) developing human capital
5) monitoring the legal and ethical performance of the corporation
6) preventing and managing crises
7) procuring resources

With only a little study, these 7 roles divide up fairly nicely to those potentially of the Gemini Board and those of the Managing Organization. The Gemini Board represents the partnership’s interest in Gemini. AURA and its boards/committees represent Gemini’s management and staff. A natural division, therefore of these roles would assign #s 1, 2, 6, and 7 to the Board and #s 3,4, and 5 to AURA. This division of roles lets the Gemini Board concentrate on strategy and resource procurement (partners, development funding, etc.) while AURA concentrates on human resources and legal operational issues. Allowing AURA the time and focus to concentrate on developing, evaluating and supporting Gemini’s human resources would be a nice benefit to this approach and would help Gemini develop and keep its best home-grown talent for future roles within the Observatory.

This division of roles also allows the opportunity for the Gemini Board to review AURA’s performance and, if we’re really being open to new ideas, to have the AURA Board, or even better, an NSF (our Executive Agency) review committee, evaluate the Gemini Board’s effectiveness. Each Board reviews Gemini in the areas of its domain, and each Board (and/or the NSF) reviews the other Board to keep everyone honest and help ensure everyone is working as optimally as possible, together, to push the Observatory forward. This sort of separation of powers is very consistent with the responsibilities of the Gemini Board, Executive Agency, and Managing Organization detailed in the partnership agreement. The Board is given the fiscal and strategic responsibilities for the Observatory as well as oversight/review of the Managing Organization. The Managing Organization is given the responsibility to develop management plans, employ key Gemini staff, and carry out Board decisions. They are thus also the likely choice for the roles of top personnel development and review within the Observatory. The roles I’ve defined could easily be agreed upon now with only a slight extrapolation necessary from the partnership agreement, and formalized, after some time to see how it works, in the next partnership agreement.


These are interesting times for Gemini, perhaps even more so than on average. Scot hopes discussions like this one happen often and broadly while we discuss and form the structure and organization of Gemini into the next decade.

Posted in General | Tagged , , , | Leave a comment

Agile development and change implementation

While I’m on the topic of change management and how it isn’t very different than plain old good management, I feel like I need to address one additional aspect that people often get wrong. Initiating a big change is hard and it’s nearly impossible to get everything right. This difficulty can cause an organization to stall in the middle of its change process, or worse still, never get its changes off the ground at all. People can worry so much about trying to get everything right at the start, that they never actually start! These people are missing a key insight, though. They are almost guaranteed to not get a big change completely right, at least not at the start. So instead of spending so much time planning perfection that you never actually get started, plan instead to make some adjustments and corrections as you go. I look at this sort of like the agile development process for software.

Instead of the traditional software design approach of getting all the customer specifications, defining all the other interfaces and requirements, producing the proper flowcharts, and pseudo-code, all before writing any actual lines of source, the agile approach relies on rapid development cycles with frequent releases between customer and vendor. These frequent releases and testing cycles allow bugs and requirement misconceptions to get caught early and fixed before they are too buried in the code to be easily changed. Fundamental tenets of agile development (thank you wikipedia) include valuing:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

While the items on the right are important, agile development places more value on those on the left. Agile development processes are now expanding beyond software to other areas of engineering and development as well. Rapid releases, real time customer interaction and results assessment, and teamwork development are all agile tenets which translate easily to other endeavors including change and general management.

Agile Development cycle

A simplified description of the Agile development process.

Planning is important, as are defining initial requirements and defining your end point in terms what outcome defines success. But planning, even 100% perfect planning, doesn’t guarantee success. In some cases there are too many variables, too many complex systems, that it is impossible to plan everything with 100% accuracy before starting. In these cases, I say borrow something from the agile programming model. Define your needs, define your end point and make a first release. Test, evaluate, repeat, until success. Don’t let lack of predictability or perfection prevent you from making a needed change. If you can’t solve everything at once, that’s OK; solve what you can and evolve from there.

Posted in General | Tagged , | Leave a comment

Change Management – Another Instance of Management 101 Getting it Wrong

Change Management is a idiom often heard these days where I work. I’m sure you know what it refers to – the process of implementing change in an organization and converting employee’s initial reactions of fear/anger/doubt to ones of discovery/understanding and ownership. The management steps used in this process involve opening up the avenues of communication to explain why the change is being made, providing training as needed, dealing with resistance, aligning employee and company needs, obtaining buy-in, implementing, and repeating – or some variations thereof.

I never bought into this approach and have recently figured out why. First off, it starts the communication and gathering of input process too late – only after the decision has been made. In reality, employees should be part of the problem formulation and solution formation from the start and not only after the powers above have declared some particular change is needed. My second objection is more fundamental in that this approach espouses certain kinds of activities and communication approaches only during major change, when in reality the proper change management approach is simply a good every day management approach. Since the default is to do today whatever you did yesterday, nearly every decision made represents some kind of change. Why do we worry about communicating with employees, aligning needs and strategies, and getting buy-in only when we see some decision as part of a change management process and not otherwise? It just doesn’t make sense. Good communication and employee involvement make good management sense always – whether or not the company is going through a major change.

It is not so much that the basic change management approach gets it wrong (and I’m sure some change management proponents adopt more sophisticated approaches which solve my implementation objections), it is more that it implies you need to worry about good management practices only during a big change and not otherwise. It is this implicit tolerance of bad management practices being the norm that I find the most troublesome and fundamentally bad for the organization. Good change management is simply good management. It doesn’t need to be separated into its own discipline.

By all means, communicate with employees, get their opinions, align their needs with those of the company, and monitor the implementation of new projects, but do this early and do it al the time! Manage this way and you’ll never have to talk about the change cycle or change management again.



Although not a particular fan of the “change management” dogma outlined above, Scot does believe in the Systems/Software Engineering approach to change control in projects. His life changed significantly for the better when he discovered CVS/SVN, for example, which he now uses extensively for his personal projects, both software and written.

Posted in General | Tagged , , | Leave a comment

Musings on career paths…

I look younger than I am.   I hear this a lot when people find out (or ask) my age.  People seem surprised to find out how old I am.  I’m never quite sure how to take this, though.  The vain part of me considers it a compliment that I look young.  The achiever part of me wonders if people think I either act young (and wonders if that’s “good or bad”, if so), figure I should know more than I do given my age, or are wondering what someone of my age is doing “only” in a position like this.  The latter thought has me thinking about career paths in general as well as my own journey that brought me to where I am now.

It seems there are two ways to “rise to the top” at an observatory (and probably elsewhere).  You either stay with the company for years and go through multiple positions as you climb that proverbial (and unfortunate, see an earlier post) organization ladder.  Or, you stay at some other company for years, then get hired in the next level up at a new company.

My career path doesn’t really lend itself well to either of those two scenarios.  Pretty much, at each new position I’ve had, I have tried to do something new, learn a new part of astronomy/the astronomy business that I hadn’t before.  These choices have given me a lot of experiences that I find very useful everywhere I go, but they haven’t made me a traditional expert in any particular area.

I guess it started with my first post-doc position.  In graduate school, I studied pulsating white dwarf stars.  My first post-graduate job, therefore, was as the only Ph.D. scientist on site at a solar observatory.  A natural progression, right?  Not really, but it was an interesting one.

From there, I went on to run operations for a global network of pulsating observers (OK, this position was directly related to my graduate work), then ran nighttime operations for an extragalactic sky survey, managed the Instrument Division at a major (foreign) observatory, then came to Gemini, my current place of employment, where to date, I’ve worked largely as a project manager for new instrument projects (with external procurements and internal work packages).

Each job I’ve held has pretty much led naturally to the next and it’s always interesting to review the chance circumstances and events which resulted in each new position, but it’s clear I’m not on a path to be an expert in any particular field.  I was trained as a scientists/research/instrumentalist.  All those skills are important for what I am doing now, but I’m not necessarily honing them in the process, either.

I do believe I am gaining breadth, though, and while I find myself envious of those that have stayed in one field and developed an incredible level of mastery, I am also pleased with my ability to speak at least somewhat intelligently, and from some direct personal experience, about software development, international project management, telescope proposal writing, observatory/project operations, instrumentation, multi-cultural work environments, machining, team management, contracting, and etc.  I’ve done a bit of each of these as part of my previous set of jobs.  And while I would love to be a detector expert, a certified project manager, or a builder of 8m-class instruments, I chose a career path (or perhaps, a career path chose me) that favors breadth of experience over individual mastery.

I’m not sure where I’m headed next, but I can see that my management tasks benefit from my broad experiences. Whether or not they’d benefit more from a more specialized expertise, I can’t say.

I’m not saying that my career path is what’s best for what I’m doing, or that there even is a best career path.  I’m just sort of thinking out loud and realizing that we all have choices to make in how/if we choose to specialize versus generalize.   Both are effective, fulfilling paths, and while mutually exclusive at any given time, can be combined over time, when the environment seems right.




Scot intends to continue to learn more about the subfields within which he works and may eventually even learn enough to say he knows what he’s doing!  Although, if that ever happens, he’ll probably move on and try something else, alas.

Posted in General | Tagged | 3 Comments

“I set early deadlines so people work hard to get done as soon as possible.”

I recently heard a project manager say something like, “I set an optimistic, aggressive schedule to make sure people work hard to meet the deadlines, otherwise, they might back off and not work as hard as they can to finish on time.”  What she was trying to say, in other words, was that she believes setting an unrealistic schedule will motivate people to work hard to finish their tasks as soon as possible. What I think setting an unrealistic schedule does is teach people that your deadlines are meaningless.  It therefore only motivates them to pay no attention to your  schedules at all.  I suppose this manager’s approach might work once, but it certainly is not going to work for long.

Would you rather work for someone who thinks she can trick you into working hard by setting unreachable deadlines, or one who involves you in coming up with a reasonable schedule and then gives you the tools you need to help you finish on time?

Posted in General | Tagged | Leave a comment