If a vendor that you’re already familiar with unveils a new software tool, do you adopt it immediately or wait to see if any bugs or problems arise?

EngineeringVendor Management
3.3k viewscircle icon5 Comments
Sort by:
Fractional CIO in Services (non-Government)2 years ago

Only if it solves a problem I have already identified. 

Lightbulb on1 circle icon1 Reply
no title2 years ago

+1

Program Manager II in Healthcare and Biotech2 years ago

I would wait to assess if any bugs or issues arise before considering adoption.

Lightbulb on1
Co-Founder in Services (non-Government)2 years ago

Do you mean Featrue or bard new tool?  From my point of view it will depend, what kind of access the tool has, what happened to data and etc, , so basically it depends :) 

CEO in Healthcare and Biotech2 years ago

We always do a check in a sandbox environment

Content you might like

What are your most important criteria when weighing a new software leadership opportunity? Which aspects of the job do you prioritize over others?

What benefits drove you to adopt agile practices? Select all that apply.

Enhanced ability to manage changing priorities32%

Accelerated software delivery52%

Increased software maintainability37%

Increased team productivity40%

Improved business & IT alignment35%

Improved project visibility25%

Improved team morale15%

Improved engineering discipline17%

Better management of distributed teams15%

Reduced project cost15%

Reduced project risk10%

Improved response to volatile market conditions8%

Other (please specify)1%

View Results

Has GenAI changed your software developers’ output?

Yes, they produce more work now19%

Yes, they produce less59%

No, their output is the same11%

Don’t know8%

Not using GenAI for software development1%

View Results

Software Engineers often get pegged as the team that says “no” or “that’s impossible”. How do you maintain a strong and trusting relationship with the product team while continuing to reset their expectations?

Read More Comments

Digital transformation isn’t just about new tools, it’s about changing how teams work. Key lessons I’ve observed: 1. Start with process bottlenecks, not technology 2. Empower cross-functional teams 3. Measure outcomes, not outputs   What has been the most surprising lesson your teams have learned during a transformation?

Read More Comments