The most appropriate steps in the Portfolio Kanban for running research spikes are probably:
1. Analysis - Spikes help clarify feasibility: Running a research spike can help clarify the feasibility of an idea and gain a deeper understanding of the problem before investing significant resources in it.
2. Portfolio backlog - Running a spike before pulling into development: Running a research spike before pulling an idea into the development backlog can be an effective way to determine its feasibility and viability before investing significant resources in it. This approach can help save time and resources by avoiding unnecessary development effort on ideas that may not be feasible in the first place.
Running a research spike can be a valuable way to validate ideas and gain a deeper understanding of problems before committing to a more substantial development effort. The Portfolio Kanban provides a framework for managing the different stages of the development process, including research spikes, to help ensure that resources are allocated effectively and that development efforts are focused on the most valuable ideas.