Unfold ItThink. Unfold. Move.Menu
Unfold ItThink. Unfold. Move.Unfold ItThink. Unfold. Move.Every quarter, someone on my team wants to adopt a new framework, database, or tool. We have no consistent way to evaluate these proposals, which leads to either 'let's just try it' experiments that create tech debt or 'no' decisions that frustrate the team. I need a structured evaluation framework.
Plan for: Create a Technology Evaluation Framework for Adopting New Tools
The RFC template becomes too long and burdensome, discouraging engineers from proposing valuable new tools.
Keep the RFC template focused strictly on the problem, alternatives, and impact. Avoid requiring exhaustive implementation details upfront.
PoCs drag on indefinitely and silently merge into production codebase.
Enforce strict timeboxing (e.g., 2 weeks maximum) and require PoCs to be built in isolated branches or sandbox environments.
Team members perceive the new process as a 'blocker' rather than an enabler.
Communicate the 'why' clearly during rollout: this framework is designed to get them to a confident 'yes' faster and fairer, rather than dealing with unpredictable rejections.
Ready to make this plan yours?
