We're about to shift to a Kanban process, but (as one would expect) there is way too much WIP already underway in the organization. If our day one Kanban board reflects the current state, it could take weeks for us to work all the WIP down to the appropriate limits, and I'm concerned that will undermine the impact on the team of the new process (because it will feel just like the current process).
We could sift through the WIP and pull a bunch of it back to the backlog. That feels like the right approach, but much of it is in QA, which will require it to skip over development when it comes back onto the board. In addition to being confusing,
Finally, I thought about a blended approach, where I'd create a (temporary) mid-process backlog before QA and pull the excess QA WIP there (with excess development WIP going back to the main backlog). Doesn't completely solve the problem, but would keep the bulk of the new process looking clean. Of course, this should also be accompanied by a cease in new development work, as it would just be adding to this mid-process backlog. I suppose no new development should be started until that backlog is cleared.
Are there other best practices and/or just better ideas?