How does your platform team gather feedback on what they build? Is it ad hoc or is there a formal process for hearing from developers?

Applications & PlatformsEngineering
854 viewscircle icon1 Upvotecircle icon2 Comments
Sort by:
Senior Director - Solution Architecture in Software11 days ago

By definition, 'platform' will serve multiple teams. So, it is good to take feedback - but I believe feedback is too late. Product manager of platform should talk to users of platform BEFORE defining roadmap of platform. And when are competing priorities from different teams, organisation interest should decide final priority. 

After features are delivered, formal feedback discussion is must to see platform is doing right job.  

Lightbulb on1
Vice President, Architecture in Finance (non-banking)6 months ago

Our COE (Center of Excellence) team bridges the developer community and platform development squads. They provide platform roadmap updates, hold office hours for feature deep dives, demos, and Q&As, and maintain communication through chat groups and surveys.

This setup allows us to engage developers closely, vet feature requests, and triage issues promptly, enabling development squads to focus on platform development. Roadmap and prioritization are informed by both architecture and COE-vetted developer input.

Content you might like

What is the importance of observability in any enterprise level application landscape having multiple applications being used for external and internal customers and deployed across multi-cloud deployments from on-prem to different clouds ?

Has your organization found success using AI tools for UX?

Yes, we’re doing this successfully20%

Too early to say — we’ve just implemented AI UX tools60%

No, AI tools were not a good fit for UX10%

N/A, we haven’t tried this10%

View Results

How long does your organization retain original systems logs used to filter SOX-related actions into a system that requires review of the logs and retains the filtered logs for seven years? Does your organization consider those original system logs records subject to record retention requirements, or supporting information used to create the SOX records?

90 Days20%

365 Days40%

3 years40%

5 years

7 years

Other (share in the comments)

View Results

How do you get your business stakeholders more invested in your team’s agile workflows?

Read More Comments

What are some clear signs that a software team needs an organizational redesign? And how would you convince the C-suite that those changes are necessary?