Lytho Workflow vs. Stack Overflow for Teams

It's a flexible program that can be molded to fit most businesses. It's geared towards agencies but we've been able to use it successfully as an in-house solution. It's pretty intuitive for the most part and is easy for new hires or clients to get up and running pretty quickly.

Incentivized

In my opinion, Stack Overflow for Teams is well suited for an organization that is on a hiring spree for the engineering teams. The reason for it is because instead of catering to doubts of new joinees individually, they can be asked to refer to the Stack Overflow and hence will save a lot of time for both new joiners as well as the existing employees.

Incentivized

• Project requests - can be tailored to fit your exact needs
• Project management - can assign tasks, track time, etc.
• Proofing - robust proofing environment that's easy for clients to learn

Incentivized

• Sharing technical solutions to problems we encounter in our internal development environment.
• Sharing best practices we find in external resources.
• Discussions on design patterns and conventions we can use in our projects.

Incentivized

• Some areas are rather clunky and repetitive when it comes to project management, like editing a template once applied.
• Once a review is live, it's very difficult to edit the reviewers unless a current tier is active.
• Pretty expensive compared to the competition.

Incentivized

• I would recommend an increased engineering focus on the Microsoft Teams integration.
• It would be nice to make more medals.
• Easier ways to earn points.

Incentivized

By consolidating the requests, project management, and proofing without features we didn't need like invoicing it was an easy fit for us. We were able to quickly develop a comprehensive workflow and the gains to efficiency were immediate. Pricing was competitive (at least at the time) and the implementation was very good as well.

Incentivized

It's easier to use Stack Overflow for Teams Q&A to maintain our knowledge base over time, over the Confluence wikis that we also maintain. You don't need to bother about folders, filenames, templates - just ask a question and answer it or get it answered. It feels less formal, so developers feel more free to add content.

Incentivized

• Consolidation of project requests has been extremely helpful.
• The improvement of campus-wide communication is hard to put a price on.
• Our team knows what is due and when at all times. We're saving a lot of time previously spent in meetings.

Incentivized

• It makes the search for answers more efficient, so devs can focus in more important things.
• Knowledge is not lost, even if people leave the company.

Incentivized