Category Archives: commentary

Doing Government Websites Right

Today, I have a piece over on Tech President about how the new UK government website – Gov.uk – does a lot of things right.

I’d love to see more governments invest two of the key ingredients that made the website work – good design and better analytics.

Sadly, on the design front many politicians see design as a luxury and fail to understand that good design doesn’t just make things look better, they make websites (and other things) easier to use and so reduce other costs – like help desk costs. I can personally attest to this. Despite being adept at using the web I almost always call the help desk for federal government services because I find federal government websites virtually unnavigable.  Often I find these websites transform my personality from happy affable guy into someone who teeters between grumpy/annoyed on the mild side, to raving crazy lunatic on the other as I fail to grasp what I’m supposed to do next.

If I have to choose between wasting 45 minutes on a website getting nowhere versus calling a help line, waiting for 45 minutes on hold while I do other work and then getting my problem resolved… I go with the latter. It’s not a good use of anyone’s time, but it is often the best option at the moment.

On the analytics front, many governments simply lack the expertise to do something as simple as Google analytics, or worse are hamstrung by privacy and procurement rules keep them from using services that would enable them to know how their users are (or are not) using their website.

Aside from gov.uk, another great example of where these two ingredients came together is over at Honolulu Answers. Here a Code for America team worked with the city to see what pages (e.g. services) residents were actually visiting and then prioritized those. In addition, they worked with staff and citizen to construct answers to commonly asked questions. I suspect a simple website like this could generate real savings on the city’s help desk costs – to say nothing of happier residents and tourists.

At some risk of pressing this point too heavily, I hope that my TechPresident piece (and other articles about gov.uk) gets widely read by public servants, managers and, of course, politicians (hint: the public wants easier access to services, not easoer access to photos and press releases about you). I’m especially hoping the good people at Treasury Board Secretariat in the Canadian Federal government read it since the old Common Look and Feel standard sadly ensured that Canadian government websites are particularly terrible when it comes to usability.

The UK has shown how national governments can do better. Let’s hope others follow their lead.

 

Playing with Budget Cutbacks: On a Government 2.0 Response, Wikileaks & Analog Denial of Service Attacks

Reflecting on yesterday’s case study in broken government I had a couple of addition thoughts that I thought fun to explore and that simply did not make sense including in the original post.

A Government 2.0 Response

Yesterday’s piece was all about how Treasury Board’s new rules were likely to increase the velocity of paperwork to a far greater cost than the elimination of excess travel.

One commentator noted a more Gov 2.0 type solution that I’d been mulling over myself. Why not simply treat the government travel problem as a big data problem? Surely there are tools that would allow you to look at government travel in aggregate, maybe mashed it up against GEDS data (job title and department information) that would enable one to quickly identify outliers and other high risk travel that are worthy of closer inspection. I’m not talking about people who travel a lot (that wouldn’t be helpful) but rather people who engage in unusual travel that is hard to reconcile with their role.

While I’m confident that many public servants would find such an approach discomforting, it would be entirely within the purview of their employer to engage in such an analysis. It would also be far more effective, targeted and a deterrent (I suspect, over time) than the kind of blanket policy I wrote about yesterday that is just as (if not more) likely to eliminate necessary travel as it is unnecessary travel. Of course, if you just want to eliminate travel because you think any face to face, group or in person learning is simply not worth the expense – than the latter approach is probably more effective.

Wikileaks and Treasury Board

Of course re-reading yesterday’s post I was having a faint twinge of familiarity. I suddenly realized that my analysis of the impact of the travel restriction policy on government has parallels to the goal that drove Assange to create wikileaks. If you’ve not read Zunguzungu blog post exploring Assange’s writings about the “theory of change” of wikileaks I cannot encourage you enough to go and read it. At its core lies a simple assessment – that wikileaks is trying to shut down the “conspiracy of the state” by making it harder for effective information to be transmitted within the state. Of course, restricting travel is not nearly the same as making it impossible for public servants to communicate, but it does compromise the ability to coordinate and plan effectively – as such the essay is illuminating in thinking about how these types of policies impact not the hierarchy of an organization, but the hidden and open networks (the secret government) that help make the organization function.

Read this extract below below for a taste:

This is however, not where Assange’s reasoning leads him. He decides, instead, that the most effective way to attack this kind of organization would be to make “leaks” a fundamental part of the conspiracy’s  information environment. Which is why the point is not that particular leaks are specifically effective. Wikileaks does not leak something like the “Collateral Murder” video as a way of putting an end to that particular military tactic; that would be to target a specific leg of the hydra even as it grows two more. Instead, the idea is that increasing the porousness of the conspiracy’s information system will impede its functioning, that the conspiracy will turn against itself in self-defense, clamping down on its own information flows in ways that will then impede its own cognitive function. You destroy the conspiracy, in other words, by making it so paranoid of itself that it can no longer conspire:

This is obviously a totally different context – but it is interesting to see that one way to alter an organizations  is to change the way in which information flows around it. This was not – I suspect – the primary goal of the Treasury Board directive (it was a cost driven measure) but the above paragraph is an example of the unintended consequences. Less communication means the ability of the organization to function could be compromised.

Bureaucratic Directive’s as an Analog Denial of Service Attack

There is, of course, another more radical way of thinking about the Treasury Board directive. One of the key points I tried to make yesterday was that the directive was likely to increase the velocity of bureaucratic paperwork, tie up a larger amount of junior and, more preciously, senior resource time, all while actually allowing less work to be done.

Now if a government department were a computer, and I was able to make it send more requests that slowed its CPU (decision making capacity) and thus made other functions harder to perform – and in extreme cases actually prevented any work from happening – that would be something pretty similar to a Denial of Service attack.

Again, I’m not claiming that this was the intent, but it is a fun and interesting lens by which to look at the problem. More to explore here, I’m sure.

Hopefully this has bent a few minds and helped people see the world differently.

There is so much joy in what we do

Hello blog.

I know it has been a a week since I posted. I want to apologize and explain it is not out of a lack of love, just a tremendous amount of travel. And of course, the fact that I also have this guy to take care of. (And yes, that is us in a plane – although he’s not with me on this trip sadly).

In fact, I want to reiterate what I said during my closing remarks at the Code for America Summit – inspired by the Hold Steady I remarked (maybe even yelled out!) that “There is so much joy in what we do.”

These communities that I’ve stumbled into, the opengov, open data, civic hackers, the people in the Code for America family, the O’Reilly Network, that activists, the entrepreneurs, and the public servants, there is so much joy in what they do. I know it doesn’t always feel that way – as one major city CIO whom I respect deeply put it to me, that highs are real high but the lows can be real low – and I know it doesn’t always come through in my writing enough.

So I wanted to say it again.

There is so much joy in what we do.

That doesn’t mean we shouldn’t do better, try harder, be more critical, but it is nice to have joy. I’d say doubly so at a time when my life is feeling a little unstrategic, and the impact of my contributions feel a little unclear, it is nice to have that joy. And it is nice to be surrounded by those who feel it too. Thank you to everyone out there who helps me feel it. I hope I help you feel it a little too.

Dave

 

What the Quantified Self Movement Says and Tech and Gender

Over the past year or two I’ve been to a couple of unconferences sessions about how people are increasingly measuring different parts of their lives: how far they run, how they sleep, what they eat, etc… As some readers may be aware, these efforts are often referred to as part of the “Quantified Self Movement.” For those readers less aware (and curious), you can watch Wired Magazine editor and quantified movement originator Gary Wolf give a brief overview in this 6 minute TED talk.

All of this sounds very geeky I’m sure. And as a general data geek and avid fitbit user I am – I suppose – part of the quantified self movement myself.

Reflecting on these (few) experiences with the movement, I find it interesting that almost every session I’ve been to has been almost entirely populated by men. I’m open to the possibility that I’ve simply been to the wrong conferences or the wrong sessions, but I’m not sure that is the case. Even looking at the quantified self Wikipedia page, virtually all the gadgets referred to deal with fitness and sleep. Obviously these are not things that men exclusively care about, but they are notable because of what is absent.

Humans have, of course, probably been quantifying themselves for as long as we’ve been around. But when I think of a group of people that have been engaged in quantifying themselves in a meaningful way,for well over a millennia,it is women.

More specifically, it is women measuring their menstrual cycles. I mean as important as losing a few pounds or getting a good nights sleep may be (and it is important to me), I’m pretty sure the stakes are much lower than preventing, or trying to get, pregnancy (now that’s a life changing event!). Indeed, given that it is hard to imagine most men having any pressing needs to measure much about their bodies on a regular basis a thousand years ago, it think it would be safe to argue that women were societies first quantified selfers.

And yet I don’t think I’ve ever seen this activity discussed, looked to as a model, or engaged in by the quantified self movement. Lauren Bacon has a great post on her own experience measuring her menstrual cycle as part of her quantified self but it is pretty rare to see women adopt that language. Given that women have been measuring their periods for years, and that there is likely a strong oral and written history to look into around this, I’d think this was a line of research or inquiry that the movement would be interested at looking into. Doubly so since it would give us a window into what a community of quantified selfers looks like, especially when its activities have been more normalized (as during some parts of our history) and marginalized (during other parts).

This all feels like a lost opportunity, and the kind of thing that happens when there are too many men and not enough women in a conversation. You want to talk about the consequences of not having women in tech – this strikes me as a great example. A rich and important history is not (sufficiently) reflected in the conversation and so important lessons and practices are potentially missed.

Maybe I’m wrong. Maybe women have been part of the quantified self movement from the beginning and that this is not a larger reflection of the challenges we face when the ratio of men and women in an industry is out of whack. But my sense is that this is actually a very nice, and potentially wonderfully quantifiable, case study around the issues of women in tech.

 

Requiring Facebook for Your News Site (or website) – the Missed Opportunity

Last week I published I blog post titled Why Banning Anonymous Comments is Bad for Postmedia and Bad for Society in reaction to the fact that PostMedia’s newspapers( including the Vancouver Sun, Ottawa Citizen, National Post, etc…) now requires readers to login with a Facebook account to make comments.

The piece had a number of thoughtful and additive comments – which is always rewarding for an author to read.

Two responses, however, came from those in the newspaper industry. One came from someone claiming to be the editor of a local newspaper. I actually believe that this person is such an editor and their comments were sincere and additive. That said, there is some irony that they did not comment using their real name, while talking about how helpful and important it is that real names/identities be used. Of course they did use an identity of sorts – their role – although this is harder to verify.

The other comment came from Alex Blonski the Social Media Director at Postmedia Network Inc.

Again, both comments were thoughtful sincere and engaging – exactly what you want from a comment, especially those that don’t entirely agree with post. I also felt like while they raised legitimate interests and concerns, they, in part, missed my point. Both ultimately ended up in the same place: that handing commenting over to Facebook made life easier for newspapers since it meant less spam and nonconstructive comments.

I agree – if the lens by which you are looking at the problem is one of management, Facebook is the easier route. No doubt. My point is that it also comes at a non-trivial cost, one that potentially sees power asymmetries in a society reinforced. Those with privilege, who have financial and social freedom to be critical, will do so. Those who may be more marginalized may not feel as safe. This tradeoff was barely addressed in these responses.

As I noted in my piece, other sites appear to have found ways to foster commenting communities that are positive and additive without requiring people to use their real identities (although giving them the freedom to do so if they wish). But of course these sites have invested in developing their community. And as I tried to stress in my last post – if you are unhappy with the comments on your website – you really have yourself to blame, it’s the community you created. Anil Dash has good thoughts on this too.

As a result, it is sometimes hard to hear of newspapers talk about people not willing to pay for the news and complain of diminishing revenue while at the same time appearing blind to recognizing that what makes for a great website is not just the content (which, especially in the news world be commoditized) but rather that community that gathers around and discusses it. Restricting that community to Facebook users (or more specifically, people willing to use their Facebook account to comment – a far smaller subset) essentially limits the part of your website that can be the most unique and the most attractive to users – the community. This is actually a place where brand loyalty and market opportunities could be built, and yet I believe PostMedia’s move will make it harder, not easier to capitalize on this asset.

I also found some of specific’s of PostMedia’s comments hard to agree with. Alex Blonski noted that they had commenters pretending to be columnists, that they were overwhelmed with spam, and claiming that Discus – the commenting system I use on my site has similar requirements to Facebook. The later is definitely not true (while you may use your real identity, I don’t require you to, I don’t even require a legit email address) and the former two comments feel eminently manageable by any half decent commenting system.

Indeed Alexander Howard – the Gov 2.0 journalist who uses the twitter handle @digiphile seems to manage just fine on his own. He recently updated his policies around moderation – and indeed his (and Mathew Ingram’s) opinions on commenting should be read by everyone in every newspaper – not just PostMedia. In the end, here is a single journalist who has more than three times the twitter followers of the Vancouver Sun (~151,000 vs. ~43,000) so is likely dealing with a non-trivial amount of comments and other social media traffic. If he can handle it, surely PostMedia can to?

 

Why Banning Anonymous Comments is Bad for Postmedia and Bad for Society

Last night I discovered that my local newspaper – the Vancouver Sun – was going to require users log in with Facebook to comment. It turns out that this will be true of all Postmedia newspapers.

I’m stunned that a newspaper ownership would make such a move. Even more so that editors and journalists would support it. We should all be disappointed when the fourth estate is unable to recognize it is dis-empowering those who are most marginalized. Especially when there are better alternatives at ones disposal. (For those interested in this I also recommend reading Mathew Ingram’s post, Anonymity Has Value, In Comments and Elsewhere from over a year ago.)

So what’s wrong with forcing users to sign in via Facebook to comment?

First, you have to be pretty privileged to believe that forcing people to use their real names will improve comments. Yes, there are a lot of people who use anonymity to troll or say stupid things, but there are also many people who – for very legitimate reasons – don’t want to use their real name.

What supporters of banning anonymity are saying is not just that they oppose trolls (I do too!) but that, for the sake of “accountability” we must also know the name of recovering sexual abuse victim who wants to share their personal perspective on a story in the comments. Or that we (and thus also their boss) should get to know the name of an employee who wants to share information about illegal or unethical practices they have seen at their work in a comment. It also means that a comment you make, ten years hence, can be saved on a newspapers website, traced back to your Facebook account and so used by a prospective employer to decide if you should get a job.

What ending anonymity is really about is power. Now, those who can comment will (even more so) be disproportionately those who have the income and social security to know they can voice their concern in public, safely. So I’m confident that this move will reduce trolls – but it will also snuff out the voices of those who are most marginalized. And journalists clearly understand the power dynamics of our society and the important role anonymity plays in balancing them  this is why they use anonymous sources to get scoops and dig up stories. So how newspapers as an institution, and journalists as a profession see narrowing the opportunity for those most marginalized to challenge power and authority in the comments section as being consistent with their mission, I cannot explain.

There are, of course, far better ways of handling comments. The CBC does a quite decent job of letting people vote up and down comments – this means I rarely see the worst trolls and many thoughtful comments rise to the top. The Globe does an adequate job at this as well. Mechanisms such as these are far less draconian the “outlawing” anonymity and preserve room for those most impacted or marginalized.

But let me go further. Journalists and editors often complain about the comments section as being wild. Well how often to they take even the tiniest bit of energy to engage their commentators? There are plenty of sites that allow anonymous comments with fantastic results – see flickr or reddit – but this is because those sites invested in creating norms and engaging their users. When has a journalist or commentator in this country ever decided to invest themselves in engaging their readers and commenters on a regular and ongoing basis in the comments section? While I’m sure there are important exceptions, by and large the answer is almost never. Indeed, I’m always stunned by the number of journalists and commentators I talk to who more or less hold much of their audience in contempt – seeing them as wild. No wonder the comment section has run amok – we can pretend otherwise but the commenters know you don’t respect them. If newspapers are not happy with their comment sections, they really have no one to blame but themselves. This is after all, the community they created, the norms they fostered, the result of investments that they made. Shluffing it all off to Facebook both runs counter to their mission but is also a shirking of responsibility (and business opportunity) of the highest order.

Of course, handing the problem to Facebook won’t solve it either. It was suggested, at last count, that over 80 million facebook accounts are fake. Expect that number to go up. But of course, the people who will be most happy to create that fake account are going to be the trolls who want to use it regularly, not the lone commentator who has an important perspective about a story but doesn’t want to tell the world who they are out of fear of social stigma or worse.

What’s worse, Postmedia has now essentially farmed its privacy policy out to Facebook. Presently that means that, in theory, you can’t be anonymous. But what will it mean in the future? Postmedia can’t tell you. They can’t even influence it.

For an organization managing discussions as sensitive as newspapers do – that is a pretty shocking stance to take. Who knows what future decisions about privacy Facebook is going to make. But here’s what I do know, I trusted the National Post a hell of a lot more to manage my comments and identity than I do Facebook because their missions are totally different. In the end, this could be bad not just for comments, but for Postmedia. Many people are already pretty uncomfortable with Facebook’s policies. I expect more will become so. Even if they don’t comment, I suspect readers will be drawn to sites that engage them more effectively – a newspapers that has outsourced its engagement to Facebook will probably lose out.

I get that Postmedia believes its job of managing comments will become easier because it has outsourced identity management to Facebook – but it has come at a real cost, one that I think is unacceptable for a newspaper. In the end, I think the quality of engagement and of discussion at Postmedia will suffer. That will be bad for it, but it will also be bad for society in general.

And that is sad news for all of us.

Added @ 9:27am PST. Note: Some Postmedia journalists want to make clear that this decision was a corporate one, not theirs.

Is the Internet bringing us together or is it tearing us apart?

The other day the Vancouver Sun – via Simon Fraser University’s Public Square program – asked me to pen a piece answering the questions: Is the Internet bringing us together or is it tearing us apart?

Yesterday, they published the piece.

My short answer?

Trying to unravel whether the Internet is bringing us together or tearing us apart is impossible. It does both. What really matters is how we build generative communities, online and off.

My main point?

That community organizing is both growing and democratizing. On MeetUp alone there are 423 coming events in Vancouver. That’s 423 emergent community leaders, all learning how to mobilize people, whether it is for a party, to teach them how to knit, grow a business or learn how to speak Spanish.

This is pretty exciting.

A secondary point?

Is that it is not all good news. There are lots of communities, online and off, that are not generative. So if we are creating more communities, many of them will also be those we don’t agree with, and that are even destructive.

Check it

It always remains exciting to me what you can squeeze into 500 words. Yesterday, the Sun published the piece here, if you’re interested, please do consider checking it out.

Lies, Damned Lies, and Open Data

I have an article titles Lies, Damn Lies and Open Data in Slate Magazine as part of their Future Tense series.

Here, for me, is the core point:

On the surface, the open data movement was about who could access and use government data. It rested on the idea that data was as much a public asset as a highway, bridge, or park and so should be made available to those who paid for its creation and curation: taxpayers. But contrary to the hopes of some advocates, improving public access to data—that is, access to the evidence upon which public policy is going to be constructed—does not magically cause governments’, and politicians’, desire for control to evaporate. Quite the opposite. Open data will not depoliticize debate. It will force citizens, and governments, to realize how politicized data is, and always has been.

The long form census debacle here in Canada was, I think, a great example of data getting politicized, and was really helped clarify my thinking around this. This piece has been germinating since then, but the core thesis has occasionally leaked out during some of my talks and discussion. Indeed, you can see me share some of it during the tail end of my opening keynote at the Open Knowledge Foundation International Open Data Camp almost three years ago.

Anyways, please hop on over to Slate and take a look – I hope you enjoy the read.

Community Managers: Expectations, Experience and Culture Matter

Here’s an awesome link to grind home my point from my OSCON keynote on Community Management, particularly the part where I spoke about the importance of managing wait times – the period between when a volunteer/contributor takes and action and when they get feedback on that action.

In my talk I referenced code review wait times. For non-developers, in open source projects, a volunteer (contributor) will often write a patch which they must be reviewed by someone who oversees the project before it gets incorporated into the software’s code base. This is akin to a quality assurance process – say, like if you are baking brownies for the church charity event, the organizer probably wants to see the brownies first, just to make sure they aren’t a disaster. The period between which you write the patch (or make the brownies) and when the project manager reviews them and say they are ok/not ok, that’s the wait time.

The thing is, if you never tell people how long they are going to have to wait – expect them to get unhappy. More importantly, if, while their waiting, other contributors come and make negative comments about their contributions, don’t be surprised if they get even more unhappy and become less and less inclined to submit patches (or brownies, or whatever makes your community go round).

In other words while your code base may be important but expectations, experience and culture matter, probably more. I don’t think anyone believes Drupal is the best CMS ever invented, but its community has a pretty good expectations, a great experience and fantastic culture, so I suspect it kicks the ass of many “technically” better CMS’s run by lesser managed communities.

Because hey, if I’ve come to expect that I have to wait an infinite or undetermined amount of time, if the experience I have interacting with others suck and if the culture of the community I’m trying to volunteer with is not positive… Guess what. I’m probably going to stop contributing.

This is not rocket science.

And you can see evidence of people who experience this frustration in places around the net. Edd Dumbill sent me this link via hacker news of a frustrated contributor tired of enduring crappy expectations, experience and culture.

Heres what happens to pull requests in my experience:

  • you first find something that needs fixing
  • you write a test to reproduce the problem
  • you pass the test
  • you push the code to github and wait
  • then you keep waiting
  • then you wait a lot longer (it’s been months now)
  • then some ivory tower asshole (not part of the core team) sitting in a basement finds a reason to comment in a negative way.
  • you respond to the comment
  • more people jump on the negative train and burry your honestly helpful idea in sad faces and unrelated negativity
  • the pull dies because you just don’t give a fuck any more

If this is what your volunteer community – be it software driven, or for poverty, or a religious org, or whatever – is like, you will bleed volunteers.

This is why I keep saying things like code review dashboards matter. I bet if this user could at least see what the average wait time is for code review he’d have been much, much happier. Even if that wait time were a month… at least he’d have known what to expect. Of course improving the experience and community culture are harder problems to solve… but they clearly would have helped as well.

Most open source projects have the data to set up such a dashboard, it is just a question of if we will.

Okay, I’m late for an appointment, but really wanted to share that link and write something about it.

NB: Apologies if you’ve already seen this. I accidentally publishes this as a page, not a post on August 24th, so it escaped most people’s view.

Roger Fisher: 1922-2012

Virtually all of my blog readers, and for that matter, much of the world, will not know that on August 25 Roger Fisher passed away.

Roger Fisher was a Harvard academic and adviser to presidents and leaders, and perhaps most importantly – because his writings touched so many people – a co-author of Getting To Yes (along with numerous other books) which outlined and made accessible interest based negotiation theory to the world.

Sadly, his wikipedia page is shockingly short on the scope and range of his work and achievements (I’ve now edited it so it reflects his accomplishments much better). There is little about his important role advising President Carter and the other principals during the negotiations of the Camp David Accords and only passing reference to his role in resolving a long-standing border dispute between Peru and Ecuador. This is to say nothing of the millions of people in the corporate, non-profit and political spheres who have been influenced by his writings and thinking. In an odd way however, the entry is perhaps fitting for a man that was – in my limited experience – exceedingly humble.

Happily a more robust description of Fisher’s accomplishments see this wonderful summary over at the Harvard Law School’s website, here’s a tiny taste:

According to Patton, Fisher’s efforts contributed directly and materially to multiple steps toward peace in the Middle East, including Sadat’s trip to Jerusalem, and the Camp David summit that led to an Israeli-Egyptian peace treaty; peace in Central America and especially in El Salvador; the resolution of the longest-running war in the western hemisphere between Ecuador and Peru; the breakthrough that enabled resolution of the Iranian hostage conflict in 1980; a fundamental reshaping of the U.S.-Soviet relationship; and the negotiations and constitutional process that led to the end of apartheid in South Africa.  (Read the full text of Patton’s tribute here.) Fisher is also recognized as the intellectual father of the “West Point Negotiation Project,” which has trained Army officers and cadets to recognize conflicts and apply the tools of principled negotiation in both peace and war.

For myself, it would not be overstating issues to say that Roger Fisher (along with Ury and Patton) changed my life. Indeed, the ideas found in Getting to Yes have been central to almost everything I’ve done for almost 15 years. Be it my work in open government, public policy, open source and open innovation, community management, or flat out negotiation consulting on things like the Canadian Boreal Forest Agreement, the ideas that make up interest based negotiation have strongly informed my thinking and made me more effective than I otherwise would ever have been. Frankly, they have made me a better person.

It is, and remains, one of my life’s great privileges that I briefly got to work with Roger. And while he remains someone who helped change the way people work, negotiate and collaborate together, the thing that I always remember about him was the incredible generosity with which he engaged everyone – including a 24 year kid fresh out of graduate school, long on dreams, and short on experience.

In late 2000 I got my first job with a Cambridge based Vantage Partners, a negotiation consulting company spun out of the Harvard Negotiation Project that Roger had helped found in 1983. Word came down from the partners that Roger (who did not work at Vantage) wanted an associate to help him plan and role out an upcoming workshop for a group of Israeli and Palestinian negotiators. Through enormous good luck (I won a draw) I was the one chosen to help him. I remember being so overwhelmed by the opportunity (could a more striking fanboy moment be imagined?). And so it was that evening when, without warning, Roger called my apartment in Cambridge to talk about the work. Getting a call from Roger Fisher was a little like having my teenage self getting a call from Bono.

But while as high as that conversation made me feel, what really struck me was how much he wanted my opinions and my thoughts about what should happen over the few days that the Israeli’s and Palestinians would be in town. I was dumbstruck that he even wanted to know what I thought, but having him honestly engage my ideas reset all my notions about how those with power can engage those who feel like they have less. Even writing this, I’m struck with how insufficiently I’ve modeled Roger’s capacity to honestly, thoughtfully and respectfully engage almost anyone who feels intimated or having less authority than you.

But the one story that I feel really sums up his character comes from his 80th birthday party at Harvard in 2002. After the dinner and speeches people were mingling and starting to drift home. But Roger and I ended up deep in conversation, discussing possible paths to peace for Israel, the Palestinians and the middle east in general. In fact we become so engrossed we did not notice that virtually everyone had left and it was really just us, and his wife, standing by the door with their jackets, looking slightly displeased.

In that moment, the pieces of Roger Fisher that I knew (again, briefly) were all in play.

Here was a man who I recall feeling personally responsible for helping secure peace in the middle east 20 years earlier. He carried an indescribable personal burden for what he felt was a missed earlier opportunity to help the region as well as a responsibility to make it right.

Here also was man that enjoyed engaging with young people and getting new opinions. Much like the story above I was struck by ho much he wanted to know what I thought. He wanted opinion, and wanted to know how I saw the facts on the ground. It was startling, rewarding, humbling, and frankly, scary, to be taken so seriously.

But finally, and maybe most importantly he was a man so dedicated to his mission of tackling great problems and fulfilling his sense of duty that he even wanted to do it on his 80th birthday. While some may see that as tragic, for me it spoke volumes about the sense of responsibility and duty with which he lived his life.

While a shocking percentage of the world has read, or learned the ideas embedded within, Getting To Yes, few of those people will have known who Roger Fisher was or how he has influenced them. For him, my sense is that was just okay. He was never interested in fame, but rather in solving the worlds most dangerous and intractable problems. While the problems I tackle are more smaller and more humble than the ones he dealt with, I hope I can bring the same dedication, insight and skill that he brought to the table.