What can we do about Workshop Remorse?

Workshop remorse

A workshop is arranged with the goal of solving a particular problem. Let’s say the problem is that the pages in a section of a website have become messy and need to be reorganised to improve the usability for visitors. The workshop uses a card sorting exercise to rearrange the existing pages and create a new structure. Everyone in the workshop accepts it and agrees the next steps.

Then… a few days after the workshop, some worries start to creep in. Things like, what if the changes affect our page search rankings, what if the changes make it harder for my customers to do what I want them to do, what if my manager doesn’t like the changes I agreed to.

That’s workshop remorse.

So then the emails start, emails that communicate those doubts and create little speed bumps. Shared among the group those worries multiply, and quickly people start to think of reasons why not to do what was they agreed at the workshop. The speed bumps grow into road blocks and everyone agrees that it would be better to wait some for seemingly connected thing to happen before we go back to solving this problem.

That’s the impact of workshop remorse.

How can we tackle it?

Every workshop should be about creating a space that has psychological safety for those involved. They should feel safe to say things they wouldn’t normally allow themselves to.

Maybe a part of a workshop should be spent talking about fears, concerns, barriers, internal agendas and organisational politics to bring this remorse to the forefront before it happens. Talk about it and tackle it.

Let’s see if by making the organisational politics visible we can challenge it. There’s no blame, we are all victims of our organisational culture and all implicit in creating it, so let’s be open about it.

Let’s see if by admitting our fears and worries we can overcome them and take control of them rather than allowing them to impact the work we want to do. It’s fine to have fears, we’re all human.

Let’s see if by talking about internal agendas we can reach some shared objectives that help everyone achieve. It’s not a zero sum game. One person doesn’t have to lose in order for another to win. We can all win if we work together.

What could we do?

We could hold a ‘Confessions time’ as part of the workshop. Maybe people would feel like it’s ok to open up.

Someone who has been workshops like this before might say: “I’m concerned that we’ll do this exercise but it’ll take so long for us to make any positive changes that we’ll all lose our enthusiasm and it’ll feel like wasted effort.”

The person running the workshop might say: “My worry is that you all won’t trust in the process and will want to feel in control of what we produce rather than allowing what users want to guide us.”

One of the less confident people in the group might say: “I’m worried that my part of business will be under-represented and I won’t achieve what I’m supposed to.”

And so everyone starts to understand how everyone else is feeling.

Then we can get on with the card sorting, because actually the workshop isn’t really about organising pages on a website, it’s really about having a safe and inspiring place to work, it’s about how we can improve the organisation one step at a time, its’ about people working together to create something awesome.

Weeknotes 102

What happened this week…

  • Meeting with the Cards and Books B & M Team to discuss cook books.
  • Reviewed Defibrillator advertising plan.
  • Tested payment interfaces for the new Online Shop.
  • Reviewed and tested file imports and exports.
  • Met with Defibrillator supplier to discuss logistics.Set up the home page for the new Online Shop.
  • Finalised the license for Magento.
  • Discussed the go live plan for the new Online Shop.

Read this week…

Doing next week…

  • Testing buying journey for the new Online Shop.
  • Building dotmailer transactional emails.
  • Meeting with the Giftware B & M Team.
  • Discussing Survival strategy, the chain of survival, and measurement.
  • Agreeing finance and logistics processes for Selling Defibrillators.
  • Meeting with the Fundraising Innovations Manager to discuss Defibrillators.
  • Mapping the customer journey for Selling Defibrillators with Corporate Partnerships.
  • Discussing Sales Invoices in AX.

Interesting stat of the week…

  • Comparing New and Returning visitors in July so far to the same dates last year, Conversion Rate for New Visitors has increased 48% and Returning Visitors has increased 38%.

In the not too distant future….

  • Defibrillator product training.

No deadlines

Scrum works for cross-functional teams of specialists that only work on one thing at a time and have everything they need within the team to complete the work.

Scrum has the #NoEstimates movement that says slicing work small enough enables teams to incrementally deliver value without requiring any kind of estimation.

But Scrum doesn’t work for multi-functional teams of generalists that work on lots of different things at the same time and have to work with other parts of the business to accomplish their goals.

I’d like to propose #NoDeadlines for modern agile teams not using Scrum and working in ways that mean the work they are doing requires collaboration with other people and teams who also have other work and different priorities, and which is often out of the teams control.

#NoDeadlines recognises that it’s impossible to accurately predict when work will be completed if it is dependent on people that aren’t part of the core team doing the work. The more people and teams involved, and the more things those teams are working on, the more impossible it becomes to accurately predict when any piece of work will be completed.

Commitment to deadlines should only be made if everything that is required to meet that deadline is within the control of the person making the commitment. If any element of the work requires input from someone who isn’t part of the team doing the work, isn’t asked to commit to the same deadline, has other priorities, works to a different schedule, or suffers no consequences from not meeting the deadline, then deadlines should not be set.

Deadlines set in these kinds of situations are at best completely arbitrary and at worst pure fantasy. Communicating fantasy deadlines to other parts of the business undermine the team when those deadlines aren’t achieved because the team needed input from other people who weren’t committed to the work in the same way.

Not setting deadlines takes the pressure off of teams from chasing unrealistic fantasy deadlines that they don’t have control over and provides psychological safety to experiment rapidly and focus on delivering value to the customers when that value is ready.

Weeknotes 101

What happened this week…

  • Volunteered at a BHF event.
  • Discussed the Sales Interface between Magento and AX.
  • Finalised t-shirt designs and briefed suppliers.
  • Discussed solutions to security issues with Freshdesk.
  • Discussed Christmas Card Marketing with the digital team.
  • Implemented a new stock counting process in the warehouse.
  • Designed onboarding emails for Selling Defibrillators.
  • Tested Magento 2 to prepare for launch.
  • Wrote Magento 2 guides for the Customer Service team.
  • Mapped Customer Service touch points for CPR and Defibs.
  • Went to a charity talk about user testing and understanding audience needs.

Read this week…

Doing next week..

  • Launching the new Online Shop.
  • Meeting with the Cards B&M Team to discuss books.
  • Producing Defibrillators range plan.
  • Planning testing selling Christmas cards on Amazon.
  • Producing Defibs content changes on the main website.
  • Testing Selling Defibs onboarding email automation.

Interesting stat of the week…

  • Comparing January to July of this year to last year, the conversion rate increased by 38.21% and Average Order Value increased by 3.73%.

In the not too distant future….

  • A new fundraising campaign.

Weeknotes 100

What happened this week…

  • Designed the home page for the new Online Shop.
  • Reviewed content across the site.
  • Had the Accessories Team monthly meeting to discuss new clothing.
  • Designed new t-shirts.
  • Magento 2 Training.
  • Quarterly Roadmap Planning Session.
  • Planned clearing old books stock.Began user testing t-shirt designs

Read this week…

Doing next week…

  • Discussing RMSP Phase 1 sales interface.
  • Discussing advertising for Christmas cards.
  • Testing transactional emails for the new Online Shop.
  • Discussing alignment between the national defibrillator network and selling defibrillators.
  • Testing finance processes for Selling Defibrillators.
  • Customer Service guide to using the new Online Shop.
  • Building onboarding emails for Selling Defibrillators.
  • Going to a talk about understanding customers through user testing.
  • Populating and testing the new Online Shop.

Interesting stat of the week…

  • In June, our average Revenue Per Visitor from referral traffic from the main website was £1.64. 17,403 users came from 878 different pages across the website.

In the not too distant future….

  • Selling furniture.

Buying and merchandising teams have always been Agile

For a Buying and Merchandising Team performing quite a traditional function for a business that is moving towards a more Agile approach, the uncertainty around impending changes could be a cause for concern. But they shouldn’t be. I think Buying and Merchandising Teams are already working in quite agile ways.

Accepting change

Merchandisers will start a year with a target for how much they think a product will sell, which they use to buy the right quantity of stock. They’ll create a plan based on last year’s sales information to suggest how much will sell, when and where (which shops), but

Merchandisers inspect the sales and adapt the replenishment of stock to shops to maximise the sales potential.

Small batches

A merchandiser could send all the stock they have out to shops at the beginning of the season, but instead, through analysis of sales patterns they break the stock down into small batches and distribute it to shops for when they need it.

Merchandisers slice the available stock into small batches.

Fast feedback

New products are introduced in a disciplined way. They are bought in smaller initial quantities, trialled in a small number of shops, and watched carefully to see how they perform. These initial reactions are then used to plan further roll-out of the product to more shops, or discontinue the product.

Merchandisers get fast feedback from customers and use it to inform how to distribute stock to shops.