Forum menu
Bit of an interesting situation developing at work , and I've got a fair bit on my shoulders, so would appreciate some views to help formulate my case.
I'm heading up Design of a strand. I am an employee. We have consultancy heading up Op Model.
I have a Design 'considerations' spreadsheet, which essentially is a high level list of stuff we need to build..be it process or tech. We are in very early days, finding feet still and this is a massive project in the making. Like, massive.
They want to have an OP model column alongside each Design entry, which is entirely sensible, plus a process considerations column, which is equally fine being a layer of the Op Model blah blah.
Question:
How would you define the scope of their 'process' column? Particularly its distinction from the work that Design does?
I know what [u]I[/u] think, but would appreciate views from others.
Bit specific, so experience of those involved in either strand of work, or the scope definition, would be appreciated.
Thanks 🙂
Que?
How massive? £100m? £500m? And I'm afraid from your description I really don't get any idea what you are trying to achieve, which makes recommendations tricky.
The question is how do would you define the scope of the 'process' layer of the OP Model strand, to be.
Edit: Additionally, how would you phrase it in a statement to make clear the difference from the process work of Design?