Any tips on how to create an engineering strategy that your team actually takes up? How do you drive adoption?

Change management and buy-in is always challenging. One of the keys to adoption is engagement. Time should be invested to ensure the team understands the reason for the strategy (“why”) and the role they play in achieving the intended outcomes (“what”). Strategies are typically articulated at an executive level so a mapping or contextualization is needed for understanding depending on the audience level. It is also useful to have the team members provide their thoughts on potential solutions (“how”) to achieve the outcomes to confirm understanding, validate alignment and also foster engagement. These engagement activities need to be continuously repeated to maintain engagement and alignment, especially as strategies are refined or evolve over time.

A strategy should be developed with the users in mind and have an objective that is clearly defined that is important to the user community. The strategy should codify part of the procurement roadmap. That roadmap should detail the plan to take your procurement services to the next level.

If the strategy takes time out of the user's already busy day without a valuable return for the user, the strategy will not be adopted. If it violates the 5-minute rule, you may have problems. The 5-minute being, if you add more than 5 minutes of work to users’ days, the users will look at the task critically, asking whether I should spend time here or on one of a dozen competing priorities.

If the user does not clearly understand and agree to that there is a clearly defined objective, the strategy will not be adopted. The user must see the value in the strategy, and that is valuable to invest time and energy supporting. 

If the strategy does not have clear baselines and measurable KPIs that are tracked and presented regularly, the strategy will not be adopted. At some point you need to say we are victorious; measurably and achievable targets are critical. 

I recommend creating an engineering strategy - what do you want to measure?
Benchmark all part of critical SDLC process - code management standards, testing, observability, resiliency, DevSecOps, change management, etc.

To be successful in encouraging adoption -
1. Define a maturity model with criteria’s measuring focus areas as mentioned above. Create a scale - level 0 indicate opportunity to improve engineering practices and level 5 being most matured implementation.
2. Assess existing applications and baseline current maturity level.
3. Create a plan and roadmap to improve each criteria.

I have found establishing these goals really pushes team be accountable and also get recognition for achieving highest matured implementations.

You're talking about change management. And I would recommend this book on that topic: https://a.co/d/04YUaEA

It starts with engagement: Involve all stakeholders in the development of the strategy so that all perspectives are considered.
Once defined the strategy has to be communicated so that purpose and direction of the strategy are clear. Training and support will help so that everyone has the knowledge and skills to comply.
Regularly monitor and evaluate compliance with the strategy. There might be gaps, there might be room for improvement.