I like finishing things – I really do. Like that adorable little thing in the photo there. Its a sock. Just a little shorty sock – ribbed cuff, afterthought heel (more on that later), top-down stockinette – nothing fancy. But, ya know what? It gave me great pleasure to finish that sock. Not because I was bored with it or that I had fallen out of love with the yarn – ohhh no. But because I like to finish things.
I’m the opposite of the people who start a thing then move on to the next before the first is quite done. The ‘oh I brought it this far’ syndrome that leaves a project not quite ready for prime time. I work with someone like that. This individual keeps saying ‘give me more projects’ and ‘how are they ever going to trust me if you don’t let me work on things’. So I let them work on something – I outline the parameters of the project then let go. When I get it back its alllllmost done – but the reports are not final or approved. And there is no process flowchart. The files are not named in any logical or repeatable manner. All of the program design is haphazard. In short – left for me to finish and present to the client.
Now, I realize that I’m the supervisor. Its my job to make sure that what goes out is correct to both internal and external clients. But, when I assign a project to someone who’s been crabbing for months about getting the client to trust them, to be able to work on projects for them only to have it not completed I get a little testy. Which is probably why I’m blowing off steam here in my blog rather than talking about knitting.
But why can’t there be an intersection between work and knitting? A knitting pattern flows from one step to the next, in a logical, defined manner to its conclusion. Sure, you can knit the pieces out of order – so what if I want to knit both sleeves of my sweater on one huge circular needle? Nobody cares. It’s pretty much the same for process. Once the process is defined, tested and installed you can run the steps out of order (well, some of them) if you so desire. There’s more than one way to reach a correct outcome. But the process, like a knitting pattern, needs to be written and tested first. All the way – start to finish – taking into account things like repeatability, end user experience (or lack thereof) and desired result with Quality Controls. Don’t sell me a poorly written knitting pattern and DO NOT give me a half-assed attempt at a client project.