DX Platform

What do you like best about the product?

The interface is easy to use. We use the "pull request"-overview on a daily basis. It's a bit unclear how often the PR's are updated though (if it's daily, hourly etc)

What do you dislike about the product?

We tried PlatformX - we tried the query functionality and it appeard to be very slow.

What problems is the product solving and how is that benefiting you?

We recently started to use Dx, so we are starting to get some insight into how well things are documented in tv2.

What do you like best about the product?

Github integration, and the insight in PRs

What do you dislike about the product?

The delay in data, we can't query data immidiately.

What problems is the product solving and how is that benefiting you?

Productivity, closer collaboration

What do you like best about the product?

One of the best things about DX is that it replaces assumptions with a clear, data-driven understanding of developer experience. Instead of relying on intuition and assumptions, DX gives us measurable, comparable insights into where friction actually exists, whether it's in tooling, documentation, cross-team collaboration, or pipelines and delivery flows.

It provides concrete data to validate whether our initiatives are truly moving the needle for product teams, giving us a much stronger foundation for prioritizing work and aligning improvements with real team needs.

As a platform domain, DX is especially valuable because it highlights where we can have the greatest positive impact across the organisation. When DX shows that certain issues (e.g., poor documentation quality) are common across the organisation, it helps us prioritise systemic improvements rather than local optimisations. It essentially gives us a shared compass for where our work will deliver the most value.

In short, DX helps ensure developer time is spent where it creates the most value, and that our technical decisions are backed by evidence rather than opinion.

What do you dislike about the product?

The main drawback is that DX still requires a certain level of maturity in how teams adopt, interpret, and act on the data. Without that maturity, insights risk becoming passive dashboards rather than meaningful drivers of change.

Also, DX is primarily designed with software engineering teams in mind. This makes it less directly applicable to more traditional infrastructure‑focused teams, where workflows and responsibilities differ from the assumptions built into the model.

It also demands a mindset shift: Teams need to actively work with the insights and continuously adjust their practices based on the data. This takes time and discipline, and there can be some initial overhead before the value becomes obvious.

In short, DX is powerful, but it requires commitment, behavioral change, and continuous refinement to reach its full potential.

What problems is the product solving and how is that benefiting you?

DX helps us understand and identify friction and bottlenecks across the organisation - based on data, not assumptions. This transparency allows us to pinpoint the areas where developer time is being lost and where improvements will have the greatest impact.

DX also highlights which issues affect the most teams and where improvements will have the largest impact. This helps us in our platform domain to focus on initiatives that raise the baseline for everyone. Whether it's improving documentation, improving shared tooling, or CI/CD foundations, DX guides us towards initiatives with the highest leverage.

DX gives platform teams and product teams a shared picture of where improvements matter most.
That alignment ensures that shared investments (e.g., in tooling, observability, or build performance) target the areas with real, proven impact.

Overall, DX enables more consistent prioritisation, stronger cross‑team alignment, and more predictable improvement in both developer experience and broader technical health.

What do you like best about the product?

As a platform leader overseeing 10+ products and delivery teams, DX is a critical lever for identifying bottlenecks, friction points, and opportunities to improve the developer experience. DX insights help us move beyond what is happening to understand the why behind productivity challenges, enabling more informed, data-driven decisions. By survey feedback (run biannually), we can continuously track developer satisfaction, delivery health, and operational effectiveness. Integration with Jira and GitHub data, helps build metrics such as cycle time by project/team/individual, epic forecast accuracy, support tickets per customer, after-hours activity, and AI coding assistant adoption—allowing us to benchmark against industry standards, improve engineering quality, and ultimately deliver better customer outcomes.

What do you dislike about the product?

We’ve integrated with Outlook Calendar to get clearer visibility into how teams balance meeting time versus deep work. Right now, the metrics roll up all meetings, and we don’t yet have a way to exclude specific meeting types. That’s an area we can explore enhancing in the future to make the insights more accurate and relevant.

What problems is the product solving and how is that benefiting you?

we use this DX Platform to pinpoint developer-experience bottlenecks and understand the root causes behind productivity challenges in one place.

What do you like best about the product?

What really stands out to me is that it’s built with empathy for engineers. It doesn’t try to micromanage individuals; it helps teams spot friction, improve flow, and have better conversations about what’s slowing them down. Used well, it becomes a shared language between engineering, leadership, and platform teams and that’s incredibly powerful.

What do you dislike about the product?

If I’m being honest, the biggest thing to dislike about tools like DX is that they can be misunderstood or misused when the intent isn’t clearly communicated.

Because DX surfaces a lot of data, there’s a real risk that some orgs treat it like an individual performance dashboard rather than a way to understand systemic friction. If teams don’t establish trust and shared context upfront, engineers may start to worry they’re being measured instead of supported, and that can easily backfire.

Another potential downside is that metrics alone don’t tell the full story. DX is great at highlighting where things are slowing down, but you still need strong engineering judgment and real conversations to understand the “why” and decide what to fix. Without that, it’s easy to end up optimizing the numbers instead of improving the actual day-to-day experience.

What problems is the product solving and how is that benefiting you?

Before using DX, capturing team feedback felt fragmented and reactive. We relied on a mix of ad-hoc Slack conversations, occasional retros, and periodic surveys. Feedback often arrived late, lacked context, and by the time patterns emerged, the window to act had already passed. It was also difficult to connect sentiment to what was actually happening in the delivery cycle, so many concerns stayed anecdotal.

With DX’s snapshotting feature, that changed in a very practical way. We had struggled to get timely, structured feedback that reflected how teams were feeling in the moment. Now we can capture lightweight, contextual snapshots tied to real events releases, incidents, and changes in process which has produced a clearer signal and faster action on real friction points.Participation improved as well, because snapshots are quick and low-effort, leading to more honest and more representative input from teams.

In terms of impact, we’ve reduced the time spent trying to interpret team sentiment by 30–40%, since the feedback is clearer and easier to synthesize. Follow-ups on DX or process issues now happen in days instead of weeks, which helps prevent small frustrations from turning into recurring problems. Leaders spend less time chasing qualitative input, and teams feel more heard, which has measurably improved engagement in retros and improvement initiatives.

Overall, DX’s snapshotting has turned feedback from a lagging indicator into a near-real-time signal, making it easier to act early and make changes that actually stick.