I'm a service designer in Scottish Enterprise's unsurprisingly-named service design team. I've been involved in the web for over 20 years, one way or another.
This week, I did something I thought I’d never do: I deceived our users. Our visitors.
Our customers.
That’s pretty much a sacking offence, so maybe I should explain.
As part of the digital first team, we’re looking for ways to get user feedback. After all, how will we know if customers think our products and services are valuable unless we ask them?
We can’t always do that face to face. Is there another way?
I'm a service designer in Scottish Enterprise's unsurprisingly-named service design team. I've been involved in the web for over 20 years, one way or another.
When businesses take on big IT projects (or any kind of big projects, I suppose), they puff their cheeks out and say, metaphorical hands on not-at-all-literal hips:
Gonna cost you guv.
They’re thinking: we’re going to have to plan this. We’ll need a risk register. We’ll have to fix the scope, gather all the deliverables, consult all the stakeholders.
Then we’ll create a PID, and a project plan. And if we get approval, and funding, we’ll start on an 18 month delivery plan that we’ve already been talking about for 6 months.
Then they’ll spend 2 months going round everyone who may have even the smallest stake in the project. They’ll seek their opinions, solicit their preferences.
Everything will be documented, in documents that will never be read by anyone.
Once all the stakeholders have been consulted, they’ll start planning. The risk register will be completed. A project plan will be drawn up. It is submitted for approval, and approval is granted.
Hey, we’ve been working on this thing for 6 months already and have delivered nothing but documentation. But we’ve already spent so much money on it that we can’t stop.
I'm a service designer in Scottish Enterprise's unsurprisingly-named service design team. I've been involved in the web for over 20 years, one way or another.
I’m part of the digital first project, the team that’s looking into new ways of working that will help Scottish Enterprise improve its projects’ performance.
One of the things the team is doing is a 12-week training course on Value, Flow, Quality. That probably doesn’t mean much to most people, but basically it’s a methodology we can use to organise ourselves and our work to deliver value to our customers, quickly and flexibly.
One of the things we looked at in our first session was why IT and software projects regularly fail (by some measures, only one project in three is successful).
I'm a service designer in Scottish Enterprise's unsurprisingly-named service design team. I've been involved in the web for over 20 years, one way or another.