Why do you want to implement those changes? Is it because as it stands currently it actually doesn’t work, or just because the status quo isn’t best practice?
> create a shared wiki and require teams to put access directions, openAPI specs, and each environment urls.
Imho this is a great change and pretty much universally applicable, but it’s not an easy one. Wikis quickly go out of date when there is no buy in from everybody involved. Also, you need to really think about the structure. The search function of some wiki tools (confluence) is famous for being awful, so make sure the wiki is well structured *and* remains that way.
> create ci/cd templates, starting with a paved path into k8s
CI/CD templates are great for some projects and awful for others. Depending on the standardization in your org in terms of tooling you may find it impossible to achieve any meaningful technology coverage for templates. My company has done a pretty good job in providing just enough scaffold to make building a CI/CD pipeline easy with libraries. We have libraries that make stuff like setting up internal package repositories, internal root CAs etc very easy and nothing more. People are quite happy with that approach.
However, a paved path into K8s and deeper into the cloud ecosystem of your choice (as implied by your status quo) is a kind of political and architectural decision I would not dare to touch in the pursuit of better developer experience.
K8s is a real beast and kind of overpowered for 95% if the instance is being used with. You need a real need for it to justify the investment required in terms of migration effort as well es engineering in maintenance (note that while managed K8s offers lift some off the maintenance burden off your shoulder, there is still a substantial amount of responsibility on your part).
> - create a quarterly summary and survey of engineers
Is this your entire job or is this some additional responsibility you plan on taking on. If the later, I’d suggest you stay away from this. I’ve seen this approach being tried several times and the result was always the same. After an initial spike in enthusiasm engagement is starting to die off while the effort required for upkeep keeps on rising.