- Agile Leadership Development
- Product Owner
Why now? What conditions in the world make this the right time for a Humanizing Work movement?
There are two key shifts that have happened in our working world that are really unique to our day. These changes require us to rethink the way we work.
Peter and Richard look at the reason behind the shift in work and practical steps you can take to humanize work individually and organization-wide.
Growth is one of the core things that motivates people in all aspects of their life.
“Work that doesn’t provide opportunities for growth is dehumanizing.”
“Energy is additive. If I’m growing at work I’ve got energy…when I get home…now I have some energy to develop other parts of my life.”
Peter and Richard talk about how they’ve seen growth motivate clients and share research and advice on how you can take next steps in your individual growth.
An editor of Dr. Dobbs magazine once wrote to me—replying to my response to an article—“All the benefits [of Test-Driven Development] could be attained equally by writing tests after the code, rather than before.”
Tests exercise software to be sure it’s doing what was intended. So, whether you use Test-Driven Development (TDD) or write unit-tests after coding, you’re presumably getting the same benefit. The safety-net gets built, either way. Right?Read More
When you think about what motivates someone within their job or work it tends to go back to what their connection is to the purpose behind their work.
“…it’s hard to imagine a motivating purpose that doesn’t impact another person. I think we are wired to care about other people.”
Richard Lawrence and Peter Green examine the theories of motivation and the core motivators they’ve found in their work with clients.
“This is why successful serial entrepreneurs, even after a big exit, go on to start something else, not because they need the money, but because they need to do meaningful work.”
If you’re not growing, do you lose interest? If you’re not pushing yourself to the edge of your ability, where the stakes are high and the outcome matters, are you able to find meaning in your work? Is doing as little work as possible with the greatest financial gain the goal?
Peter Green and Richard Lawrence tackle the relationship (or conflict) between ease and meaning in this episode of the Humanizing Work Show.
This week, we launched the Humanizing Work Show. In episode 1, we summarize what we mean by Humanizing Work and where the phrase came from.
Humanizing Work is about shaping work to fit people. When people thrive at work, teams and organizations thrive.
Humanizing Work has four key themes:
- Creativity — people need to exercise autonomy, to create and change their world
- Collaboration — people need connection, and they accomplish greater things in collaboration with others
- Impact — people are motivated by making a difference in other people’s lives
- Growth — work should cause people to grow and should provide a space for people to express their growth
Humanizing Work Show Episode 1: What does it mean to "Humanize Work" ?A lot of people are punching the timecard, getting their paycheck and going home... 'I can't wait until Friday' or 'Oh no, I've got the Monday blues,' seems like a typical conversation between friends and colleagues. It has become routine to complain about work.
Peter Green and Richard Lawrence talk about what meaningful work can look like through four major themes they've witnessed in working with hundreds of clients and organizations.
Location: Infinite Monkey Theorem, Denver, CO
In future episodes, we’ll go deeper into specific ways to flesh out these themes in organizations and we’ll talk with people who are doing creating Humanizing Work in their own organizations. Subscribe on Youtube or Facebook to get notified when each new episode is released.
Participants in our courses are sometimes surprised to find out that they have work to do in advance of the course. Most of our live, interactive courses involve a self-guided, online prerequisite course. Here’s why. Read More
Next year I’ll likely be teaching Essential Test-Driven Development to a team that includes about 50% COBOL programmers. I told the client I’d look for a good object-oriented (OO) primer for those developers to read in advance. As you can imagine, it’s tough to “unit-test” software that doesn’t have clear “unit” boundaries. COBOL relies on a lot of global state, and this appears to be true for this client.