DX Platform
DXReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
247 reviews
from
External reviews are not included in the AWS star rating for the product.
Excellent tool for developer experience teams and leadership!
What do you like best about the product?
Gives a clear view of the experiences of your engineering teams, where they see issues and where they're happy.
What do you dislike about the product?
Can occasionally be difficult to understand which parts of the product line give what capabilities - no problem if you license the whole thing, though.
What problems is the product solving and how is that benefiting you?
* Helps to direct roadmaps for developer experience and platform infrastructure teams
* helps engineering directors to address organizational issues that cause friction or churn, PR review velocity for example
* helps engineering directors to address organizational issues that cause friction or churn, PR review velocity for example
Actionable insights to drive impact
What do you like best about the product?
We have been using DX for more than 2 years now.
DX is a platform where the entire engineering org and the developer enablement function in particular get both quantitative and qualitative insights on the overall ecosystem.
As a team responsible for developer productivity, my team and I use DX on almost a daily basis.
The most important usecase are the quarterly surveys which provide important qualitative data around developer sentiment across various drivers as well as CSAT scores for the tools we provide to the engineering org. Besides this, there are tools such as Data Studio which give a unified view by aggregating data from multiple systems such as github(builds, commit, review turn arounds), datadog (incident related data) and JIRA to derive further quantitative insights which help us validate the qualitative data from the surveys.
We also use tools such as Studies (on-demand, specific surveys), PlatformX to send surveys on specific events such as users encountering an error or users loading a specific documentation page etc.
The initial setup and integration with systems such as github, datadog, JIRA was very easy and has been very stable.
The support team has always been very helpful and feature requests have very low turn around time.
DX is a platform where the entire engineering org and the developer enablement function in particular get both quantitative and qualitative insights on the overall ecosystem.
As a team responsible for developer productivity, my team and I use DX on almost a daily basis.
The most important usecase are the quarterly surveys which provide important qualitative data around developer sentiment across various drivers as well as CSAT scores for the tools we provide to the engineering org. Besides this, there are tools such as Data Studio which give a unified view by aggregating data from multiple systems such as github(builds, commit, review turn arounds), datadog (incident related data) and JIRA to derive further quantitative insights which help us validate the qualitative data from the surveys.
We also use tools such as Studies (on-demand, specific surveys), PlatformX to send surveys on specific events such as users encountering an error or users loading a specific documentation page etc.
The initial setup and integration with systems such as github, datadog, JIRA was very easy and has been very stable.
The support team has always been very helpful and feature requests have very low turn around time.
What do you dislike about the product?
What I'm listing here are not exactly the faults of the tool but things that I feel could be misused.
If DX is rolled out to an org without an exec sponsorship and some top down push, then the platform team rolling this out might not get enough traction, hence it is very important to ensure buy-in from the leadership.
Another possible anti-pattern that can happen is that some leaders could blindly chase specific numbers without applying the full organisational context which might trigger gaming of the system.
If DX is rolled out to an org without an exec sponsorship and some top down push, then the platform team rolling this out might not get enough traction, hence it is very important to ensure buy-in from the leadership.
Another possible anti-pattern that can happen is that some leaders could blindly chase specific numbers without applying the full organisational context which might trigger gaming of the system.
What problems is the product solving and how is that benefiting you?
Compared to traditional surveys, we get very high response rates (95%+) and the benchmarking against similar sized companies helps us gauge which areas of work do we focus more towards.
Getting CSAT on internal tools helps us understand where to focus more.
DX helps us also gather various metrics at team/repository/service level around aspects such as change failure rates, deployment frequency, review turn around times, usage and adoption of AI tools etc.
Getting CSAT on internal tools helps us understand where to focus more.
DX helps us also gather various metrics at team/repository/service level around aspects such as change failure rates, deployment frequency, review turn around times, usage and adoption of AI tools etc.
Finally an easier way to start measuring team performance
What do you like best about the product?
Ease of use, implementation. Easy to backfill data, no need for adding stuff to ci/cd.
What do you dislike about the product?
I wish you could more easily create and modify the out of the box dashboards to fit your needs. The custom dashboards feel like a much worse experience, then the default dora oens for exmaple.
What problems is the product solving and how is that benefiting you?
Measuring DORA, and other developer productivity metrics.
Super valuable visibility into the problems of the engineering org
What do you like best about the product?
Very good surveys/snapshots with insights into industry best practices and some customization. Has created strong alignment between engineers and executives on the actual biggest problems in the organization. Very nice to have all data of Github and Jira in one database. The AI allows to quickly do ad-hoc queries (as long as they aren't too complex).
What do you dislike about the product?
Doesn't allow to group Github repositories/services by tags to teams (which is something that Wiz for example supports, not a competitor but similar space). While it doesn't promote unhealthy practices like stack ranking ICs on output metrics, it does make it very easy to do so. Requires mature leadership that doesn't fall into this trap.
What problems is the product solving and how is that benefiting you?
Shows quantitative and qualitative data about engineering organization.
Enhancing our learnings with DX
What do you like best about the product?
DX is extremely transparent with the information collected. Not only can you conduct various scope and size surveys and create dashboards, it is visible to all. Additionally, it is easy to view and find the information you are looking for, as well as manage teams and various attributes for team members.
What do you dislike about the product?
The questions in the studies are geared a bit towards tech vs. full product, design and tech organizations which requires a few custom questions to ensure we are being inclusive for our organization. The DX team is always willing to help us manage this and expand our reach.
What problems is the product solving and how is that benefiting you?
In order to gain understanding of our organization, with year-over-year impact metrics, we find that DX is a great tool to help us capture our product, design and tech team members sentiment. Additionally, utilizing separate smaller surveys to deep dive into areas of need. DX pushes us to focus on top areas provided by the entire team and helps with recommended approaches.
GetDX: From Subjective to Strategic
What do you like best about the product?
Adopting GetDX has been a transformative step for our organization. It’s dramatically simplified how we report on and communicate developer productivity, which was once a recurring, challenging conversation steeped in subjectivity.
As a team that follows the advancement of industry research in this area, it’s reassuring to see the work of thought leaders like Nicole Forsgren, Jez Humble, and Margaret-Anne Storey directly inform the foundations and evolution of the DX platform. This credibility has been key in internal evangelization, enabling us to point internal stakeholders with a deeper interest to rigorous studies and comprehensive write-ups.
Importantly, as the platform continues to evolve, e.g. introduction of the Core 4, it hasn't necessitated major refactors to our integrations, allowing us to evolve with minimal overhead. Overall, DX has taken a large portion of the effort out of how we measure, communicate, and ultimately improve developer experience, and pushes us be more strategic and less reactive.
As a team that follows the advancement of industry research in this area, it’s reassuring to see the work of thought leaders like Nicole Forsgren, Jez Humble, and Margaret-Anne Storey directly inform the foundations and evolution of the DX platform. This credibility has been key in internal evangelization, enabling us to point internal stakeholders with a deeper interest to rigorous studies and comprehensive write-ups.
Importantly, as the platform continues to evolve, e.g. introduction of the Core 4, it hasn't necessitated major refactors to our integrations, allowing us to evolve with minimal overhead. Overall, DX has taken a large portion of the effort out of how we measure, communicate, and ultimately improve developer experience, and pushes us be more strategic and less reactive.
What do you dislike about the product?
Snapshot Triage flow is not particularly useful. EMs find it confusing and the Studies feature suffices for followups. Team management could be more intuitive.
What problems is the product solving and how is that benefiting you?
GetDX has solved the challenges of accurately measuring developer productivity, surfacing experience insights, and communicating engineering health across our organization. By combining system data with developer feedback, integrating fragmented tools, aligning with evolving research, and offering peer benchmarking, it has provided us with a unified, actionable view that is driving real improvements in productivity and engineering satisfaction.
Easy to use, helpful metrics
What do you like best about the product?
We've been using DX for DORA metrics as well as getting feedback about developer experience. Everything has been easy to set up and use. Support has been very quick and helpful.
What do you dislike about the product?
We ran into some hurdles initially with data correctness, but support helped us get past them relatively quickly.
What problems is the product solving and how is that benefiting you?
My team works on internal tools for other developers and it helps us collect useful data on what our users want.
DX provides a unique lens into the day-to-day lived experience of the teams I support.
What do you like best about the product?
Quantitative metrics were easy to deploy, and easy to understand. Qualitative metrics (snapshots) dovetail in quite nicely. Our account liaison is an excellent partner.
What do you dislike about the product?
There is a lot of data and it comes with a steep learning curve. Making sense of all of the information, learning what's applicable and what's not, takes a long time.
What problems is the product solving and how is that benefiting you?
I manage the Developer Experience team, and so my primary focus is ensuring that our developers are at optimal functionality. I care very much about the lived experience and well-being of our employees, as well as their output and velocity. DX gives me insight into all of this.
CTO
What do you like best about the product?
qualitative + quantitative approach to PD
What do you dislike about the product?
ease of implementation, price, lack of user engagement from engineers
What problems is the product solving and how is that benefiting you?
hearing feedback directly from on the ground developers, that can be linked with quantitative data to make informed decisions.
Quantitative and Qualitative insights all in one
What do you like best about the product?
Qualitative survey gives good insights into how the team works and where to focus on. You can also tailor the survey to what is more apprporiate for you company.
What do you dislike about the product?
Its not easily solved but the quantify the productivity of engineering teams is something that will need to improve over time. No one has cracked this.
There are good insights that you can make specific actions against.
There are good insights that you can make specific actions against.
What problems is the product solving and how is that benefiting you?
Improving the productivity of the team and find insights into what changes we can make to improve the way we work.
showing 151 - 160