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

• Requests - Request forms are set up so that certain fields are required and there's a minimum turnaround time. This prevents others from submitting an incomplete request or requesting things last minute.
• Proofing - Chasing after people to approve a proof is always a pain, but the simplicity of Lytho Workflow makes it less of a pain. I can quickly remind people in the route to review the proof by clicking a button.
• Templates - I use templates so that a list of tasks is created for me when I accept a job. It also creates a timeline for when each task needs to be done.

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

• Not being able to permanently delete inactive/old users (i.e. employees that are no longer with the company).
• Search filtering features are lacking.
• Not being notified when someone replies to my comment without @ mentioning me.

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

• I wasn't working for the company when they first started using Lytho Workflow workflow, so I can't say what impact it has had. However, I do see the product as a necessity in the fast-paced environment that is retail marketing. The introduction of the new "change request" feature has saved countless hours of miscommunication and confusion when project objectives change.

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