It’s Been One Hot Minute!

Yes, that’s right folks, and after several years of neglect, we have finally launched a newly updated website and store.

We here at Mammoth are committed to keeping the website updated with fresh content, including merchandise, blog posts, job opportunities, and more importantly – featured work. We have several unannounced awesomely unique plans for the website, our social media, and our new initiative – Brainstorm, a series of spontaneous digital events and live group discussions.

Noboby Cares, Work Harder.

Everyone wants to be a winner. But building a successful project isn’t just something that will come without a little hard work. Really want to get ahead? There are certain principles that need to put into place.

The first step to succeeding at anything is defining what success means. We all have a different vision of what success looks like. We have to take a long, hard look at what it is we hope to achieve and why. This thought process will allow you to set specific goals and requirements, which will give you and your team direction. This extreme focus is necessary to keep you and your team motivated to improve processes, achieve goals, and deliver products.

Once you and your team know what you want to achieve, it’s time to get to a bit of hard work. If you want a project to really succeed, you must be willing to do whatever it takes to make your requirement goals come true. Don’t be ruthless or unethical in your efforts to “deliver”. But you and your team must to be willing to work longer and harder than anyone else – competitors, customers, vendors. With team buy-in, you need to do the “things” that no other organization wants to do. You and your team may need to make personal or social sacrifices so that you all can work towards the end result, making sure everyone involved is working the right/efficient way.

It’s a simple fact: as your team continues project development, there will undoubtedly be hurdles and challenges at certain points in the development lifecycle. Instead of dismissing or shying away from challenges, try to learn from them. Often enough, when you really take the time to consider the obstacle at hand, it informs you about some way in which you could improve the overall project. If you and the team are willing to make improvements, you’ll ultimately create a more robust and well-built project or solution. Success rewards consistency. This means that even when things get tough – actually, especially when things get tough – you and your team need to keep going. Do what you can to keep the team motivated, including creating a fun working environment. But don’t give up. Success is truly the result of diligence and steady practice.

The Next Mobile App Update Will Be Great

Continuously coming up with great ideas is difficult, but convincing people, clients, and employees to act upon them is even harder. The concept of implementing an idea in a nice user friendly mobile package is, in a nutshell, hard.

Mobile applications demand change. Even if your mobile application is undeniably awesome and perfect, it will force someone, somewhere to question “why did they do it this way?”. Many people, including your mobile application users, do not like change, and fear change. The functionality of your mobile application that you find so appealing may be precisely what makes your mobile application so difficult for people to use.

Some business owners and product managers fear change so much that they structure their work lives around avoiding it. Healthy and successful organizations make change easier than their less successful competitors. Leaders in these places for smart people not only encourage positive change to happen, but expect it at all levels of their organization. It requires more work and maturity for these business owners to make this kind of environment successful, but when they pull it off, smart people are systematically encouraged to be smart. Organizational changes, ideas, and modifications happen all the time: in hallways, in the cafeteria, in meetings. Why shouldn’t the extension of your business – your mobile app – operate in the same manner?

Great product revisions and changes need some thinking about execution and delivery. Saying “we should build realtime inventory tracking and automatic invoicing into our next application release” counts as a great and interesting idea. It’s a good start, but implementation won’t be successful until there’s both some logic for how to make it real within reasonable limitations, and some level of detail in how to convert the abstract functionality (realtime inventory tracking) into tangible and measurable items for your mobile application users.

Most of the time it’s not worth pushing out a revision to your mobile application until you’re able to answer some of the basic pragmatic questions. What problem and/or issue does the update solve? Why should this problem and/or issue be solved now? (Application errors, etc.) What evidence (user feedback, etc.) is there that the problem and/or issue is real? Do you have an installable beta application that includes revisions, so that testing and feedback can be done by a subset of your userbase?