Setting an Intention

This is what I said to open an all day creative exercise with our leadership team, and founder (Debbie) focused on our long term future…

The most important thing I have to say is Debbie and I have talked about this and we give you complete permission to let go of the day to day. We’ve given ourselves this one day out of 261 work days in a year to think about the future. Monday we can get back to the work of operating Stride.

As for today, I hope we make this a safe space. Your feelings are yours and you have a right to them. Your dreams are yours and you have a right to them. To borrow from open space. “The people who are here are the right people. Whatever happens today is the only thing that could.”

In terms of outcomes, today is an exercise in collective imagination. Everything we create here will be documented. We will share it with Striders. We will spend the next 3-6 months learning from them how to connect our plans to their aspirations. Ultimately I want every Strider to be able to use our vision to find more meaning in their day to day work.

This work is a piece along with our 2022 goals and the work you’re doing to mature our sales and consulting strategies. When we plan 2023 we will have the information we need to set meaningful and measurable long range goals and iterate on our corporate strategy.

Any questions on the outcomes or the day?

I want to talk about setting an intention. How much it guides our actions.

2035 is 14 years from now. 2007 is 14 years ago. In 2007, I was VP Eng at Oxygen Cable.

I’d been there eight years and we’d built a high performing Agile team: product, engineering and design. Our CEO had just started to work with us as product owner on a line of consumer software. She was looking to recapture her original mission to become a content brand for women.

Our first attempt was a kind of Pinterest two years before Pinterest. We were in beta and then over a weekend Oxygen was acquired. They new owner wanted the audience and carriage. But they didn’t want the mission.

It was pretty inevitable how things were going to play out. My team was scouted as individuals, each assigned separate transition responsibilities. I spent a decent amount of time writing down what I thought about the experience and laying out what I cared about.

About the acquisition process, I said:

We haven’t been rewarded or treated as one (team) but as individuals in service of organizations. A focus on citizens and cities – not neighborhoods.

What is difficult for the integrators to discern are the values, practices, spirit and reputation that allow this team to attract and develop new talent even as individuals move on.

About building software I wrote:

You can optimize construction practices as much as you want but if there is no discernible need for what you’re building…
The goal is not to build crap well. It is to find a way each day to do less and less crap and more and more not crap.

On professional ethics:

Ethical behavior is not about being right or infallible.

Human judgment is fallible but we must act to create the most benefit and least harm in accordance with the principle that others have as much right to joy, fulfillment and dignity as we do ourselves.

If harm results from even our best efforts we must take responsibility. No one is perfect and there are always mitigating circumstances but there are also no excuses.

Finally, I wrote this personal manifesto:

In my decisions and actions, I balance the following:

  • I care about the people who use what I create.
  • I care about the quality of what I create.
  • I care about the people with whom I create.
  • I honor my commitments to my employer.
  • I am loyal to people who have earned my loyalty.
  • I provide for my family.

I reflect on my decisions and actions to avoid:

  • negligence,
  • incompetence,
  • deception,
  • waste, and
  • harm.

Agile practice is a means to these ends.

Putting out what I cared about and what I wanted to create in the world influenced my actions and shaped my career. It became the filter with which I made decisions, informed what I learned and who I sought out to learn from. It guided my interactions with co-workers, what work I was willing to take, and with whom I built working relationships.

It’s why I met Debbie. It’s why I hired her prior company and then Stride. It’s why I joined Stride. It’s why I challenged fundamental assumptions about our business. And it’s why I’d chosen to work for someone who cared enough about Striders to listen to me and take a risk with all of us.

We have been handed the opportunity to make decisions with a broader frame of reference and longer timeline. And we can move more quickly because we have each other.

Even still, it can as long as it takes. Because the incremental steps are worth it and the journey is worth it. It’s worth it to live true to the vision, values and people you care about. To see a future that is better than the present and to work for it together.

Stride will evolve along with us. It will continue to attract inspiring people to work with us and rise to meet our aspirations to achieve our life goals, make a contribution to society, and help improve conditions on our planet.

The existential joys of agile practice: people over process

At Agile NYC I presented a pecha kucha. 20 slides. 20 seconds per slide. This is the third of four parts.

People over process

Cathleen P. Black, who took over as New York City schools chancellor in January, at the Tuesday meeting of the Panel on Educational Policy.

Robert Stolarik for The New York Times

Cathie Black was Chancellor of New York City Schools for three months. She was hired despite having no education experience and no affinity for public schools, parents, teachers and students because she was, “an excellent manager”.

I love that agile doesn’t celebrate management. It relies on individual contributors. It relies on community.

painting by Eiko JudyThe oozy failure wrapped in the chocolatey success of agile is when we focus on process mechanics and lose sight of people.

If we do, our practice becomes arbitrary and abstract.

There’s a study that claims the best and worst performers have more in common with each other than those in the broad middle.

NYC Lego First PitsWhile the best are energized by their caring and use that passion to drive to the best outcomes, the worst are demoralized and ruined by it.

The indifferent middle, they just plug away.

When we impose a process upon a workplace to avoid failure. We rob the best performers of opportunities to engage and care.

Sunset Big IslandWe preclude the best in an attempt to avoid the worst and ensure mediocrity.

I acknowledge that successful products can emerge from awful workplaces. And that that good teams often create failed products.

But working in a way that tears down talented people’s desire for work is tragic. To repeatedly do this this is to sap the world of its limited supply inspiration, creativity and joy.

Power, dissent, and bullying in software developer communities

Grassroots developer communities form around shared values in dissent against institutions and norms that dehumanize their work and diminish their efforts. They attack these orthodoxies with humor, heretical thinking, and hard work.

This benefits society when developers defy those with greater power. It harms society when developers bully people with less power.

At the ThoughtWorks sponsored Agile East, Martin Fowler spoke to his post, SmutOnRails.

Part of the community was offended by a presentation at the GoGaRuCo (Golden Gate Ruby Conference). Others fought back saying that no offense was meant, the presenter apologized, and that the tone was in the spirit of the Rails community.

(T)he view of the rails leadership seems to be this: that the objections to the presentation are yet another attempt to foist empty corporate values on the thriving Rails ecosystem… (more)

This debate is not unique to the Rails community. It reminds me of concerns my friend, Luke Melia, raised over jokes and behavior at the first Austin Alt.NET. Martin Fowler links off to a similar controversy in the Flash community.

It is also not unique to developer communities but developers in particular need to be concerned about the outcome.

Women, African Americans and Hispanics are under-represented in IT and even more so in software development. In 2001-2002 74.4% of software developers were men. 78% of those men were white.

In 1986 the percentage of women in CS programs peaked at 37%. The percentage of women in computer science programs has gone down since then.

In 2001-2, only 28 percent of all undergraduate degrees in computer science went to women. By 2004-5, the number had declined to only 22 percent. — What Has Driven Women Out of Computer Science?, NY Times

There were 15,000 women in CS progreams in 1986. Riding natural cycles this number was not matched again until 2003. This latter number contains a higher percentage of non-resident aliens who will not necessarily contribute to the US workforce.

This despite higher percentages and numbers of women acquiring college educations than men. In 2007, 33% of women 25-29 held a four year degree or higher versus 26% of men. 55% of graduates with four year degrees or higher aged 25-29 were women.

Women are even receiving the majority of degrees in science and technology. They have shown steady progress in biology, chemistry, physics, mathematics and engineering.

Metrics can be misinterpreted but these quantitative measures support a stunningly obvious anecdotal observation. US software developers are a white male enclave.

This is a power imbalance and we developers are part of the problem.

Isolation is a key factor for a higher attrition rate among women and minorities, said Teresa Dahlberg, director of the Diversity in Information Technology Institute at UNC Charlotte. People tend to associate with “like communities,” where people have similar backgrounds and interests, she explained. — Computer science lacks women, minorities, SD Times

So when we behave in a way that marginalizes and intimidates talented women and minorities, we abuse power. We become bullies. We are oppressors.

“There is a good amount of research that shows that women are judged more harshly than men, for hiring, evaluations and promotions,” she added. “Virginia Valian [author of “Why So Slow? The Advancement of Women”] shows this for women in science, technology, engineering and math faculty jobs.” Virginia Valian is a professor at Hunter College. — SD Times

Part of the problem may be a perception that software development doesn’t contribute enough to society. To the degree this perception is true it is damning. To the degree it is just a perception we have work to do as advocates.

Our actions need to be judged not by our intentions but by the outcome.

Requisite variety within our teams remains an essential enabling condition for sustained innovation.

Access to technology is growing across all tiers of class, race and gender both in the US and overseas. Diverse teams can better address our market and build software better adapted to our end users.

A more diverse workforce provides the kind of social change that will help us create a more humane workplace for developers.

Finally, anything that limits the number of able US software developers hurts our ability to compete.

When developer communities marginalize women and minorities, we conspire to isolate ourselves from the larger society. We defeat our own attempts to change the power structures around us and improve our lot and our output.

By the time he was your age…

John Maeda has just been named the new president of the Rhode Island School of Design.

I’ve only met Mr. Maeda once — unless you count childhood visits to his family’s tofu bakery in Seattle. If you are what you eat, some protein in my bones is the product of Maeda creativity.

Anyway, I’m a tremendous fan of his approach to design and life. He continues to be a role model for embracing new challenges.

Let go, go on

Jean-Paul S. Boodhoo has a great post on creativity:

Here is the great thing about top tier developers. They don’t care about dropping all of their secrets, techniques and practices in front of you because these things are all a result of one thing, Creativity… (more)

Some close off for fear their gifts will be stolen. Others engage — confident their best ideas and greatest contributions lie ahead.