Quick Left, Inc.

Quick Left, Inc.

What can others learn from how you conceived of and designed your mobile solution or application?: 

When we approach designing a solution for a problem, we don’t look to check a box. When it comes to customer problems, we pave ‘cow paths’. We look for established wide-spread customer behavior and try to codify it. To that end, we don’t deliver solutions as quickly as customers want us to but we deliver a much more minimal solution to begin with. The second thing is when we do decide to pave a cow path, we don’t need to do it all at once. We spend a lot of time distilling what the problem is and focusing on what is the info you’re looking to relay. Once you figure out what that problem is, the person who looks up that info isn’t always the person who needs to consume it. Deconstruct it until you know what the true answer is - are they the consumer or are they relaying it to someone else? If they are doing the later, then cut to the chase. We navigate who we’re building Sprintly (or any software project) for and sometimes it takes longer to ship something. For example, we could say “Yes, I could add that button but there are 49 other people wanting a button and now we’d be up to 50 buttons on that page.” Most don’t wait until cow paths aren’t well-worn and that’s when UX goes to hell. That’s our approach to product development, UI design and UX.

Please describe how the concept for your mobile solution or application came about, and what research, information, inspiration, etc. informed it.: 

Basically, Joe Stump, the CPO of Quick Left, has a business degree and ended up a backend programmer. Joe cannot only speak developer but also can understand SWOT or revenue analysis. He is the so-called UN negotiator between the business person and developer. This led to Joe constantly being brought in for consulting and engagement deals. While great for our consulting business , this allowed us to ‘clone’ Joe and help others build amazing software. He built Sprintly to codify the things that he was doing anyway—diagnosing what was wrong with the development or product development lifecycle in businesses. So in essence, he built it so you wouldn’t have to hire a ‘Joe Stump.’ 

How does your mobile solution or application take advantage of the unique device capabilities, contexts of use, modes of use, and other factors to create a new and valuable experience or utility?: 

Sprintly, a product by Quick Left, is an Agile, B2B SaaS Application tool created to power a more productive relationship between development teams and their management. By designing Sprintly to be more transparent, flexible and usable than competitive products, cross-functional teams can reliably deliver higher quality software products. Visit Sprintly at sprint.ly. 

Taking that clean slate approach, mobile has disrupted the traditional way software has been created. We too have done the same, empowering business people (and developers) by giving them the tools to develop better software no matter where they are, we are disrupting the way software is produced. 

In what ways has your mobile solution or application benefited the lives and/or work of its users in ways that weren’t previously possible?: 

30% of Sprintly customers are nontechnical and were never using these types of tools before to try to manage software development projects. We are giving confidence to nontechnical business people to make more educated technical decisions. We’ve had people say they are 2-3x more productive because there is transparency by design in the SaaS tool . Reducing meetings, increasing efficiencies and having people rethinking our team. We had a nontechnical customer tell us that he felt like the head coach of a football team but had to stay in the locker room while the game was being played and wait for a report. Now he feels empowered enough to be ‘in the game.’ How amazing is that? We are able to create better software because business people for the first time are able to create software easily. There’s also higher levels of trust due to transparency in the software platform.

If applicable, how did you adapt your solution or application to differing platforms?: 


At Sprintly, we have this opinion that ticket information is the ‘dark matter’ of companies. It comes from all over the place but they are all connected in some form or fashion. We’ve looked at step 1 which is to get all dots in one place to begin correlating them. You should be able to complete tickets on phones, emails, fax machine, etc. We need to be able to ingest as much as humanly possible—to make many dots and then correlate them. By allowing several integrations on several platforms, we are able to continue to improving our ticketing system and get Sprintly in the hands of more developers and their management team. 

How might your mobile solution or application serve as inspiration or a starting point for future innovations for mobile platforms?: 

I think what we’ve done—and whether it’s mobile or not—we questioned basic assumptions in our field of SaaS project management platforms. They all look the same, but the great thing about mobile is that it’s a clean slate. Different form factors, different basis for interaction and you’re forced by the very nature of the tiny screens and must fundamentally answer those basic questions. Just because it’s been done that way for the last 10 years, doesn’t mean you have to continue doing it that way.