Sources of Urgency

Sometimes I wish we were in the hardware business.  Why?  It’s not the margins, that’s for sure.  It’s because hardware businesses usually have externally-imposed deadlines that create urgency in an organization around deliverables.

If you are making a chip that Dell is putting in all of its boxes, and your contract with Dell stipulates that the chip will be ready for testing on X Date and for shipping on Y Date, you darn well better hit the deadline.  If you are making software that gets installed or pre-loaded on all Samsung TVs, same thing.  Maybe it’s not the hardware business per se, but you certainly don’t see this kind of mentality in SaaS businesses very often, either because of the lack of true OEM and ship dates, or because of the now fluid nature of agile software development.

Without that kind of externally-imposed deadline, instilling true urgency gets a lot harder for a leader.  Sure, you can stick an arbitrary deadline out there and rally people to work towards it, but it’s much harder to define the consequences of missing the deadline.  Since there are in many cases no tangible and immediate business consequences, it feels a little more hollow for a leader to say “Why?  Because I said so.”  Yes, you have firing as the ultimate accountability tool in your toolkit, but again, it’s hard to feel good about using that tool when the deadline is arbitrary.

Probably the default method most companies like ours have settled on over the years is around quarterly goals.  That kind of cadence removes the arbitrary part of the problem, but it doesn’t remove the tangible business consequences part of the problem – and often, it doesn’t align with actual project deadlines.  Public companies probably can use quarterly financial results as something more tangible, but those often don’t align with deliverables quarter for quarter.  Customer conferences or marketing events can be other deadlines as well, which are less arbitrary.

I realize my blog is usually more about sharing stories than asking questions, but in this case, I’d love to hear from any reader who has a good answer to this very important management challenge.  If I get a great response, I will reblog it!

Book Short – Blink part III – Undo?

I just finished reading Michael Lewis’s The Undoing Project: A Friendship That Changed Our Minds, and honestly, I wish I could hit Life’s Undo button and reclaim those hours.  I love Michael Lewis, and he’s one of those authors where if he writes it, I will read it.  But this one wasn’t really worth it for me.

Having said that, I think if you haven’t already read both Malcolm Gladwell’s Blink (review, buy) and Daniel Kahneman’s Thinking, Fast and Slow (review, buy), then it might be worth it.  But having read those two books, The Undoing Project had too much overlap and not enough “underlap” (to quote my friend Tom Bartel) – that is, not enough new stuff of substance for me.  The book mostly went into the personal relationship between two academic thinkers, Daniel Kahneman and Amos Tversky.  It also touched on some of the highlights of their work, which, while coming out of the field of psychology, won them a Nobel prize in Economics for illuminating some of the underlying mechanics of how we make decisions.

The two most interesting pieces of their work to me, which are related in the book, are:

First, that human decision-making is incredibly nuanced and complex, and that at least 25% of the time, the transitive property doesn’t apply.  For example, I may prefer coffee to tea, and I may prefer tea to hot chocolate, but that doesn’t necessarily mean I prefer coffee to hot chocolate.

From the book, “When faced with complex multidimensional alternatives, such as job offers, gambles or [political] candidates, it is extremely difficult to utilize properly all the available information.” It wasn’t that people actually preferred A to B and B to C and then turned around and preferred C to A. It was that it was sometimes very hard to understand the differences. Amos didn’t think that the real world was as likely to fool people into contradicting themselves as were the experiments he had designed.  And the choice created its own context: Different features might assume greater prominence in the mind when the coffee was being compared to tea (caffeine) than when it was being compared to hot chocolate (sugar). And what was true of drinks might also be true of people, and ideas, and emotions. The idea was interesting: When people make decisions, they are also making judgments about similarity, between some object in the real world and what they ideally want. They make these judgments by, in effect, counting up the features they notice. And as the noticeability of features can be manipulated by the way they are highlighted, the sense of how similar two things are might also be manipulated.”

Second, what Kahneman and Tversky called Prospect Theory, which is basically that humans are more motivated by the fear of loss as opposed to the greed of gain.  I’ve written about the “Fear/Greed Continuum” of my former boss from many years ago before.  I’m not sure he knew about Kahneman and Tversky’s work when he came up with that construct, and I certainly didn’t know about it when I first blogged about it years ago.  Do this experiment – ask someone both of these questions:  Would you rather be handed $500 or have a 50% chance of winning $1,000 and a 50% of getting nothing?  Then, Would you rather hand me $500 or have a 50% chance of owing me $1,000 and a 50% chance of owing me nothing?  Most of the time, the answers are not the same.

For fun, I tried this out on my kids and re-proved Prospect Theory, just in case anyone was worried about it.

Anyway, bottom line on this book – read it if you haven’t ready those other two books, skip it if you have, maybe skim it if you’ve read one of them!

As I mentioned in last week’s post, I’m rebooting my work self this year, and this quarter in particular.  One of the things I am doing is getting back to basics on a few fronts.

Over the holiday break, as I was contemplating a reboot, I emailed a handful of people with whom I’ve worked closely over the years, but for the most part people with whom I no longer work day in day out, to ask them a few questions.  The questions were fairly backward looking:

1.       When I was at my best, what were my personal habits or routines that stand out in your mind?

2.       When I was at my best, what were my work behaviors or routines that stand out in your mind?

3.       When our EC was at its best, what were the team dynamics that caused it to function so well?

I got some wonderful responses, including one which productively challenged the premise of asking backward-looking questions as I was trying to reboot for the future.  (The answer is that this was one of several things I was doing as part of Rebooting, not the only thing, and historical perspective is one of many useful tools.)

Although the question clearly led itself to this, the common theme across all the answers was “back to basics.”  Part of evolving myself as a CEO as the company has grown over the years has been stopping doing particular things and starting others intentionally.  I try to do that at least once a year.  But what this particular exercise taught me is that, like the proverbial boiled frog, there were a slew of small and medium-sized things that I’ve stopped doing over the years unintentionally that are positive and productive habits that I miss.  I have a long list of these items, and I probably won’t want or need to get to all of them.  But there are a few that I think are critical to my success for various reasons.  Some of the more noteworthy ones are:

• Blogging, which I mentioned in last week’s post as an important way for me to reflect and crystallize my thinking on specific topics
• Ensuring that I have enough open time on my calendar to breathe, think, keep current with things.  When every minute of every day is scheduled, I am working harder, but not smarter
• Be more engaged with people at the office.  This relates to having open time on the calendar.  Yesterday I sat in our kitchen area and had a quick lunch with a handful of colleagues who I don’t normally interact with.  It was such a nice break from my routine of “sit at desk, order food in” or “important business lunch,” I got to clear my head a little bit, and I got to know a couple things about a couple people in the office that I didn’t previously know
• Get closer to the front lines internally.  Although I’ve maintained good external contacts as the company has grown with key clients and partners, our multi-business-unit structure has had me too disconnected from Sales and Engineering/Product in particular.  This one may take a couple months to enact, but I need to get closer to the action internally to truly understand what’s going on in the business
• Get back to a rigorous use of a single Operating System.  I’ve written a lot about this over the years, but having a David-Allen style, single place where I track all critical to do’s for me and for my team has always been bedrock for me.  I’ve been experimenting with some different ways of doing this over the last couple years, which has led to a breakdown in Allen’s main principle of “put it all in one place” – so I am going to work on fixing that
• Reading – while I have been consistently and systematically working my way through American history and Presidential biographies books over the years, I’ve almost entirely stopped reading other books for lack of time.  A well-balanced reading diet is critical for me.  So I’m working in some other books now from the other genres I love – humor (Martini Wonderland is awesome), architecture (see last week’s post on The Fountainhead), current events (I’m in the middle of Michael Lewis’ The Undoing Project and next up is Tom Friedman’s Thank You For Being Late), and business books (about to start Kotter’s A Sense of Urgency)
• Like reading, doing something creative and unrelated to work has always been an important part of keeping my brain fresh.  Coaching little league has helped a lot.  But I need to add something that’s more purely creative.  I am still deciding between taking guitar lessons (I halfway know how to play) and sculpting lessons (I don’t know a thing about it)

That’s it for now.  There are other basics that I never let lapse (for example, exercise).  But the common theme of the above, I realize now that I am writing it all out, isn’t only “back to basics.”  It’s about creating time and space for me to be fresh and exercise different muscles instead of grinding it out all day, every day.  And that’s well worth the few minutes it took me and my friends to work up this list!

Hopefully I’ll have more to say on the general topic of rebooting in another week or two as January craziness sets in with our annual kickoff meetings around the world.

Book Short:  Scrum ptious 

I just finished reading Scrum: The Art of Doing Twice the Work in Half the Time, by Jeff Sutherland and JJ Sutherland. This reading was in anticipation of an Agile Facilitation training my executive team and I are going through next week, as part of Return Path’s  Agile Everywhere initiative. But it’s a book I should’ve read along time ago, and a book that I enjoyed.

Sutherland gets credit for creating the agile framework and bringing the concept scrum to software development over 20 years ago. The book very clearly lays out not just the color behind the creation of the framework, and the central tenets of practice again, but also clear and simple illustrations of its value and benefits.  And any book that employs the Fibonacci series and includes Theodore Roosevelt’s “Man in the Arena” quote — my all-time favorite — is off to a good start by me.

I’ve always appreciated a lot of the underlying philosophy of Agile, such as regularly checking on projects, course correcting in response to feedback from customers or other stakeholders, and working hard to remove any impediments to progress in real time.

One of the author’s most poignant points is that “multitasking makes you stupid.”  I hadn’t focused in the past how agile allows you to clear away context shifts to focus on one task at a time, but that’s another great take away from the book.

Our Agile Everywhere initiative, which is designed to improve productivity across the organization, as well as increase accountability through transparency, is even more critical in my view after having read this book.

The thing that I am left struggling with, which is still very much a work in progress for us, and hopefully something that we will address more head on in our training next week, is the application of the agile framework to teams that are not involved in the production of a tangible work product, such as executive or other leadership teams.  That is something that our Agile Everywhere deployment team has developed a theory about, but it still hasn’t entirely sunk in for me.

I can’t wait for next week’s training session!  If you have any experience applying the agile framework to different types of teams in your company I’d love to hear more about it in the Comments.

Today marks Return Path’s 16^th anniversary.  I am incredibly proud of so many things we have accomplished here and am brimming with optimism about the road ahead. While we are still a bit of an awkward teenager as a company continuing to scale, 16 is much less of an awkward teen year than 13, both metaphorically and actually. Hey – we are going to head off for college in two short years!

In honor of 16 Candles, one of my favorite movies that came out when I was a teenager, I thought I’d mark this occasion by drawing the more obvious comparisons between us and some of the main characters from the movie.  My apologies to those who may have missed this movie along the way.

Why we are like Samantha (Molly Ringwald):  No, no one borrowed our underpants. But we can’t believe that people forgot our birthday either.

Why we are like Farmer Ted / The Geek (Anthony Michael Hall):  Meet my co-founder, George Bilbrey. I mean that with love.

Why we are like Jake (Michael Schoeffling):  Meet my other co-founder, Jack Sinclair. The shy, good looking one.

Why we are like Long Duk Dong (Gedde Watanabe):  We have only been in our newest business, Consumer Insight, for five minutes, but we already have a whole bunch of dates.

Why we are like Grandpa Fred (Max Showalter):  We’ve been around long enough to know the ways of the world, not to mention all the good wisecracks in the book.

There you have it. Year 17, here we come!

The Value of a Break

I’ve written before about our sabbatical policy as well as my experience with my first sabbatical five years ago.

I just got back from another sabbatical. This one wasn’t 100% work-free, which breaks our rule, but after a few false starts with it, when I realized a few weeks before it started in January that I either needed to postpone it again or work on a couple of things while I was on a break, I opted for the latter.  The time off was great. Nothing special or too exotic. A couple short trips, and lots of quality time with Mariquita and the kids.

Re-reading my post from my last sabbatical now, I realize I have re-learned those same three lessons again — that I love my job, my colleagues, and what we are working on.

But I also recognized, in three different ways, the value of a break this time around maybe more than last time.  Maybe it’s that I’m five years older or that I’ve been doing the job for five more years.  Maybe it’s because the last couple of years at work have been incredibly intense and both physically and mentally taxing.  But regardless of cause, the outcome is the same — I return to work today rested, healthy, a little tanner, a few pounds lighter, and with more clarity, resolve, and ideas for work than I’ve had in a long time.

Not only did I recognize this with Return Path on my sabbatical, but during my sabbatical, I also reengaged with two organizations (Princeton and the Direct Marketing Association) where I sit on boards and used to be extremely active but have been pretty dormant for a couple of years. The perspective I gained from that dormant time not only gave me new energy for both, but I think very focused and creative energy that I hadn’t seen in a couple of years.

Even with a little work sprinkled in, 6 weeks off and disconnected from emails, the office, and regular meetings is a blessing that I hope everyone gets to experience at some point in his or her career.

The Best Place to Work, Part 7: Create a Thankful Atmosphere

My final installment of this long series on Creating the best place to work (no hierarchy intended by the order) is about Creating a thankful atmosphere.

What does creating a thankful atmosphere get you?  It gets you great work, in the form of people doing their all to get the job done.  We humans – all of us, absolutely including CEOs – appreciate being recognized when they do good work.  Honestly, I love what I do and would do it without any feedback, but nothing resonates with me more than a moment of thanks from someone on my exec team or my Board.  Why should anyone else in the organization be any different?

This is not about giving everyone a nod in all-hands by doing shout-outs.  That’s not sustainable as the company grows.  And not everyone does great work every week or month!  And it’s not about remembering to thank people in staff meetings, either, although that’s never bad and easier to contain and equalize.

It is about informal, regular pats on the back.  To some extent inspired by the great Ken Blanchard book Whale Done, and as I’ve written about before here, it’s about enabling the organization to be thankful, and optimizing your own thankfulness.

Years ago we created a peer award system on our company Intranet/Wiki at Return Path.  We enable Peer Recognition through this.  As of late, with about 350 employees, we probably have 30-40 of these every week.  They typically carry a $25 gift card award, although most employees tell me that they don’t care about the gift card as much as the public recognition.  Anyone can nominate anyone for one of the following awards, which are unique to us and relevant to our culture:

• EE (Everyday Excellence) -is designed for us to recognize those who demonstrate excellence and pride in their daily work.
• ABCD (Above and Beyond the Call of Duty) -is designed for us to recognize the outstanding work of our colleagues who go Above and Beyond their duties and exemplify exactly what Return Path is about
• WOOT (Working Out Of Title) -is designed for us to recognize those who offer assistance that is not part of their job responsibilities.
• OTB (On The Business)-is about pulling ourselves out of day-to-day tasks and ensuring we are continually aligned with the long-term, strategic direction of the business.  We make sure we’re not just optimizing our current tasks and processes but that we’re also thinking about whether or not we should even be doing those things.  We stop to think outside of the “box” and about the interrelationship between what we are doing and everything else in the organization.  In doing so, we connect the leaves, the branches, the trunk, the roots and soil of the tree to the hundreds of other trees in the forest.  We step back to look at the big picture
• TLAO ( Think Like An Owner)-means that every one of us holds a piece of the Company’s future and is empowered to use good judgment and act on behalf of Return Path.  In our day-to-day jobs we take personal responsibility for our products, services and interactions.  We spend like it’s our own money and we think ahead.  We are trusted to handle situations like we own the business because we are smart people who do the right thing.  We notice the things happening around us that aren’t in our day-to-day and take action as needed even if we’re not directly responsible
• Blue Light Special  is designed for us to recognize anyone who comes up with a clever way to save the company money)
• Coy Joy Award is in memory of Jen Coy who was positive, optimistic and able to persevere through the most difficult of circumstances.  This award is designed to recognize individuals who exemplify the RP values and spread joy through the workplace.  This can be by going above and beyond to welcome new employees, by showing a high degree of care and consideration for another person at RP, by being a positive and uplifting influence, and/or making another person laugh-out-loud.
• Human Firewall is awarded if you catch a colleague taking extra care around security or privacy in some way, maybe a suggestion in a meeting, a feature in a product, a suggestion around policy or practice in the office.

In the early days, we read these out each week at All-Hands meetings.  Today at our scale, we announce these awards each week on the Wiki and via email.  And I and other leaders of the business regularly read the awards list to see who is doing what good work and needs to be separately thanked on top of the peer award.

Beyond institutionalizing thanks…in terms of you as an individual person, there are lots of ways to give thanks that are meaningful.  Some are about maximizing Moments of Truth.  Another thing I do from time to time is write handwritten thank you notes to people and mail them to their homes, not to work.  But there are lots of ways to spend the time and mental energy to appreciate individuals in your company in ways that are genuine and will be noticed and appreciated.  To some extent, this paragraph (maybe this whole post) could be labeled “It’s the little things.”

That’s it for this series…again, the final roundup for the full series of Creating the Best Place to Work is here and individual posts are here:

1. Surround yourself with the best and brightest
2. Create an environment of trust
3. Manage yourself very, very well
4. Be the consummate host
5. Be the ultimate enabler
6. Let people be people
7. Create a thankful atmosphere

Anyone have any other techniques I should write about for Creating the Best Place to Work?

I gave a presentation to a few hundred Return Path employees in January at an all-hands conference we did called “How to Manager Your Career.”

The presentation has three sections — The Three Phases of a Career, How to Get Promoted, and How to Wow Your Manager.

While it’s not as good without the voiceover and interactivity, I thought I’d post it here…see the presentation on Slideshare.

As I said to my audience, if there’s one thing to take away from the topic, it’s this:

Managing your career is up to one, and only one person – you. 

It doesn’t matter how great a corporate culture you have, or how supportive your manager is.  You’re the only person who cares 100% of the time about your career, and you’re the only person with a longitudinal view of what you love, what you’re great at, where you’ve been, and where you want to go.

How to Wow Your Manager

Last week, I talked about how to Wow your employees.  Now I am going to discuss the converse of that – How to Wow your Manager.  Why Wow your manager?  Even if you are senior leader in an organization, the Wow factor is still important.

What impact does a Wow have?  It sends the signal that you are on top of things.  Symbolism is important.  It also advances the cause further and faster.  Why do you want to foster Wow moments with your team?  High performing teams have a lot of Wow going on.  If all members of a team see Wow regularly, they are all inspired to do more sooner, better.

Here are my top 10 examples on how to WOW your manager, along with the intended impact:

1. Show up for every check-in with the full agenda – send it a day or more ahead (Give your manager time and space to prepare)
2.  When you are asking your manager to communicate something (an email to the team, a reference letter, etc.), draft it for him or her (Editing is much easier than creating)
3.  Do a start-stop-continue analysis once a year on all of your key activities (Make yourself as efficient and effective as possible – that’s your responsibility as much as your manager’s)
4.  Own your own development plan and check in on it at least quarterly (Those who own their own career paths progress more quickly down them)
5. Read a relevant business book and ask your manager to discuss insights with you (Staying current with best practices in your field – books, articles, blog posts, videos, mentors, lectures –  is key in a learning organization)
6.  Dress for success – even casual can be neat and “client ready” (Your presence has an impact on those around you.  There’s no reason anyone should ever have to comment on your clothes, your hair, or any aspect of your personal hygiene)
7. Respond to every email where you are on the TO line within a day, even if it’s to say you will respond longer form later (At Return Path,  you have to be in the jet stream of communications. Otherwise, you find yourself in the exhaust of the jet stream)
8. End every meaningful interaction by asking for informal feedback on how you’re doing and what else you can be doing (Again, part of being in a learning organization…and taking more tasks on is always a sign that you are ready for more responsibility)
9. Do something that’s not required but that you feel is a best practice (This shows you’re on top of your game.  One example:  I send the Board a summary, the details, and the YoY trending of all of my expenses every year.  I don’t have to, but enough CEOs out there have high profile expense problems that I decided it’s a good practice.  They all LOVE it)
10.  (If you have staff reporting into you) Show up for every check-in with  your manager with a list of all staff issues and highlights (You need to bubble things up, both good and bad, so your manager is on top of his or her overall team and (a) is never surprised by events, (b) knows how best to handle skip-level communications, and (c) can think more broadly about resource deployment across the organization)

Another CEO with whom I trade notes on the craft of running a company asked me this question the other day, and I thought the answer would make a for a good blog post.  Any product team (or other kind of team) who has Agile practices, does some kind of a Daily Standup (DSU) meeting in which each team member reviews progress against goals for a given period and highlights issues where he or she is blocked and needs help.  I wrote about Return Path‘s journey to implement Agile across the whole company last year here.

My meeting routines have been shaped over the years but the current versions are largely influenced by Lencioni’s Death by Meeting, which is worth a read. My blog post isn’t all that helpful about this specific subject, but it’s here.  Anyway…here’s what I wrote to my friend:

I love our DSU. We do it at 11 eastern because we have people in Colorado and California on it. We just make the time. We block 15 minutes, but most people block the full :30 and sometimes a small sub group will need to stay late to cover something in more depth (we call that the after-party or the 16th minute). If I had everyone in the same time zone, I would do it at 8:30 or 9:00. 

We usually just “run the calendar” at the DSU. What’s everyone doing today, anything notable from yesterday, anything people need broader quick hit updates on, especially things that are cross-team. It’s great daily connectivity. We have tried to run the exec team like a true agile team in the past with cards and demos, etc., but that didn’t really work other than the occasional time when all of us were working on something together (e.g. Annual budgeting and planning), since a lot of our work as leaders is down, not across. 

We do the meeting Tuesday through Friday. We probably cancel 1 a week on average if too many people have to miss it. People know it’s a priority and not to schedule over it unless unavoidable, but sometimes travel, client conflicts, etc. invade. 

Mondays we still do our Weekly Tactical for an hour. I have a whole standing agenda format for that (as well as our Monthly Strategies for 2-3 hours and Quarterly Offsites for a couple days). I find that the Weekly Tactical actually goes much better with the four DSUs because we don’t have to spend time checking in on the basics…so we are much more effective in using that time on bigger items like sales forecast and recruiting review, progress against major initiatives and OKRs, having other people come in and present things to us, etc. 

Running a Productive Offsite

A couple OnlyOnce readers asked me to do a post on how I run senior team offsites.  It’s a great part of our management meeting routine at Return Path, and one that Patrick Lencioni talks about extensively in Death by Meeting (review, book) – a book worth reading if you care about this topic.

My senior team has four offsites per year.  I love them.  They are, along with my Board meetings, my favorite times of the year at work.  Here’s my formula for these meetings:

–          WHY:  There are a few purposes to our offsites.  One for us is that our senior team is geographically distributed across 4 geographies at the executive level and 6 or 7 at the broader management team level.  So for us, these are the only times of the year that we are actually in the same place.  But even if we were all in one place, we’d still do them.  The main purpose of the offsite is to pull up from the day-to-day and tackle strategic issues or things that just require more uninterrupted time.  The secondary purpose is to continue to build and develop the team, both personal relationships and team dynamics.  It’s critically important to build and sustain deep relationships across the Executive Team.  We need this time in order to be a coordinated, cohesive, high trust, aligned leadership team for the company.  As the company has expanded (particularly to diverse geographies), our senior team development has become increasingly critical

–          WHO:  Every offsite includes what we call our Executive Committee, which is for the most part, my direct reports, though that group also includes a couple C/SVP titled people who don’t report directly to me but who run significant parts of the company (7-8 people total).  Two of the four offsites we also invite the broader leadership team, which is for the most part all of the people reporting into the Executive Committee (another 20 people).  That part is new as we’ve gotten bigger.  In the earlier days, it was just my staff, and maybe one or two other people as needed for specific topics

–          WHERE:  Offsites aren’t always offsite for us.  We vary location to make geography work for people.  And we try to contain costs across all of them.  So every year, probably 2 of them are actually in one of our offices or at an inexpensive nearby hotel.  Then the other 2 are at somewhat nicer places, usually one at a conference-oriented hotel and then one at a more fun resort kind of place.  Even when we are in one of our offices, we really treat it like an offsite – no other meetings, etc., and we make sure we are out together at dinner every night

–          WHEN:  4x/year at roughly equal intervals.  We used to do them right before Board meetings as partial prep for those meetings, but that got too crowded.  Now we basically do them between Board meetings.  The only timing that’s critical is the end of year session which is all about budgeting and planning for the following year.  Our general formula when it’s the smaller group is two days and at least one, maybe two dinners.  When it’s the larger group, it’s three days and at least two dinners.  For longer meetings, we try to do at least a few hours of fun activity built into the schedule so it’s not all work.

–          WHAT:  Our offsites are super rigorous.  We put our heads together to wrestle with (sometimes solve) tough business problems – from how we’re running the company, to what’s happening with our culture, to strategic problems with our products, services and operations.  The agenda for these offsites varies widely, but the format is usually pretty consistent.  I usually open every offsite with some remarks and overall themes – a mini-state-of-the-union.  Then we do some kind of “check-in” exercise either about what people want to get out of the offsite, or something more fun like an envisioning exercise, something on a whiteboard or with post-its, etc.  We always try to spend half a day on team and individual development.  Each of us reads out our key development plan items from our most recent individual 360, does a self-assessment, then the rest of the team piles on with other data and opinions, so we keep each other honest and keep the feedback flowing.  Then we have a team development plan check-in that’s the same, but about how the team is interacting.  We always have one or two major topics to discuss coming in, and each of those has an owner and materials or a discussion paper sent out a few days ahead of time.  Then we usually have a laundry list of smaller items ranging from dumb/tactical to brain-teasing that we work in between topics or over meals (every meal has an agenda!).  There’s also time at breaks for sub-group meetings and ad hoc conversations.  We do try to come up for air, but the together time is so valuable that we squeeze every drop out of it.  Some of our best “meetings” over the years have happened side-by-side on elliptical trainers in the hotel gym at 6 a.m.  We usually have a closing check-out, next steps recap type of exercise as well.

–          HOW:  Lots of our time together is just the team, but we usually have our long-time executive coach Marc Maltz from Triad Consulting  facilitate the development plan section of the meeting.

I’m sure I missed some key things here.  Team, feel free to comment and add.  Others with other experiences, please do the same!