What are some ways to get software developers more engaged with the business value that their work delivers for the company?

I'd like to add, make the results and achievements of the software visible to the programmers. I know, that not in every case, this is possible, but when it comes to controls, robotics or any other type of comparable solution, demonstrate the final product / solution also once, if possible to show, what the lines of code really achieve at the end.

Based on my experience, I want to share a few pragmatic tactics that have worked well to connect engineers with business value:

Make value visible
 1. Give each squad a clear North Star and 2–3 business KPIs (e.g., revenue per user, retention, cost-to-serve). Every story links to one KPI.
 2. Add a one-line value hypothesis to each ticket: “We believe this will move [metric] from X→Y by [date].”
 3. Update the Definition of Done: telemetry + feature flags + experiment plan. Instrument from day one.

Bring engineers closer to customers
4) Quarterly customer shadowing: support rotations, sales calls, and usability sessions. Rotate engineers; share call clips.
5) Give self-serve access to outcome dashboards (adoption, conversion, cycle time, churn drivers).

Bake outcomes into the process
6) Prioritize by impact (ICE/RICE) and show the score + assumptions in the backlog.
7) Dual-track discovery: engineers co-own problem statements/PRDs; reserve ~10% time for discovery spikes.
8) Run a monthly Customer Value Review: demo outcomes vs baseline; pair data with a customer quote.

Align incentives and recognition
9) Include business impact (and learning from experiments) in performance reviews—not just velocity.
10) Close the loop with a 1-page Outcome Card for each release: Problem → Bet → Result (metric delta) → Learning → Next step.