It depends on who you are. If you are very small it won't be worth the money. If you have a very cranky site with nested tables coming out of every orifice, maybe you should look at a replatform or desktop rewrite first. If you have a site with vast numbers of custom content pages, it will work but may not be cost effective. Moovweb is well suited to you if you need the ability to control mobile experiences and respond to changes in mobile and the demands of mobile aware executives who want to move more quickly than your current IT processes allow. It is well suited if you need something quickly but also want the option to bring mobile development and support in-house some time in the next year or two (which you should). It is well suited if your desire to improve a responsive experience has been thwarted by internal fears over the impact that it might have on desktop. It is well suited if you want to experiment on mobile but do more than just change the color of a button or make a font larger. It's very good at letting a UX team try things out and see what real customers do.
Using it in the application support team is worth it as it is capable of carrying a lot of information. But using it for a Service Desk operation might not be of much use as it won't be used up to its full potential and will be costly as compared to other alternatives available in the market.
Moovweb takes the time to really understand your needs and challenges and is willing to work with and address them. They are partners during and AFTER implementation.
Moovweb and their implementation partner 64Labs has a fantastic response time and work ethic. They really will do what it takes.
Moovweb takes the time to share their product road map with customers.
Depending on how your site is built and maintained, there may be a different solution that will be a better option for your business and customer needs.
At the end of the day, this is another layer that is added to your development plan and time to ensure updates work across multiple devices. Moovweb is really good about the turn-time for these updates, but there still needs to be the added QA step for M&T optimization per release.
Providing admins/devs with easier mechanisms for providing businss stakeholders with self-service admin capabilities across the platform
Tutorials on how to be the best at reporting in servicenow
Guided tour functionaltiy is a bit rigid and could use more workflow capabilities
Making it easier to push form variables to the user so there is more context when providing an approval. The out of box approval UI/form is terrible in my opinion.
Personally as a Mobile Architect I am a huge proponent of building mobile-first responsive websites. I will always fight for a lobby for businesses to build sites with all devices in mind and not focus their attention on desktop driven sites which are then adaptively scaled to meet the demands of the business, in my opinion leading to a never ending cycle of building separate media queries to compensate for every device the business chooses to market to
Everybody in the company is happy to use ServiceNow. All people are happy to use a user-friendly web tool in order to open IT incidents. IT people can easily support people with a stable and solid tool.
As a regular user of the ServiceNow platform, including the incident management, change management and enterprise application management modules, I find that I am able to competently use the platform with minimal training and assistance. User guides are available from the vendor if required. The customisable front-end that we use in the organisation as an ordering tool for internal IT services is very easy to use, and makes searching for the required IT service simple for business users.
Good set of customer success people combined with the flexibility to use high-quality onshore partners if workload increases at busy times. I think Moovweb's support efforts are pretty solid.
We have many levels of interaction with ServiceNow. The first line of support sometimes is not equipped to resolve more complex issues, but the escalation process is clearly defined and followed with limited friction. Our account team is very responsive and willing to brainstorm ideas to improve and increase usage. We also have direct interaction with product teams to see previews of new features and at times to provide input to influence implementation details.
Don't spend weeks in design. Because of the way the technology works nuances of design can change very quickly further down the line. We have changed the look of the product list for a client a week before launch.
Push for getting the project into UAT within four weeks of the kickoff of the project. There are few retailer projects that need to take more than that. In my experience the more concentrated the timeline the more effective the implementation.
Check that there are no major changes planned on desktop during the time of your implementation (another reason to keep the development to four weeks).
If you have custom mobile content requirements, get them to your implementer at the start. Moovweb is great at heavy-lifting existing content, but your implementer will need to recommend solutions for custom content that will need to be tested. Get these requirements out at the start.
Make a list of your desktop plugins. Moovweb can handle them all, but they can be handled in different ways
If you have Paypal/Google Wallet and want it on mobile as part of your project, talk about that early on.
This is the only mobile technology we have used. We went through an extensive research and vetting process. In the end Moovweb was the best choice for technology and business needs. We considered the following companies: Moovweb,Mobify, Usablenet, Mad Mobile, SKAVA, Wompmobile. Forrester has a mobile infrastrucutre services report that could be very helpful.
ServiceNow is by far a better tool over Remedy. Its ability to integrate so seamlessly to so many tools allows for plenty of opportunity to streamline and improve processes. Servicenow has intuitive flows that allow you to quickly pivot if process change. Its adaptiveness is what makes it far better solution over Remedy
1. It is not great when they can't seperate apps/products from a particular sku, forcing you to make a business case for a larger portion of functionlity than your current business case seeks to address. 2. ServiceNow reps are able to work with you when economies of scale are projected out. They are willing to start at a desired tier and provide pricing at applicable upgraded tiers
Very easy to use. Capture more data from the Incident and problem management. Easier to escalate and following the change management process to resole the issues.
The implementation was 4 months from start to finish. Mobile is about 10% of our visits today and our mobile revenue for the first half is about $200K so we will have a payback in 1 -2 years.
Moovweb is not the most economical solution out there. It is one of the most comprehensive for sites needing all their content available for mobile.
Ensuring good service support internally and externally has triggered opportunities to sustain good links with everyone and opened the door to more sales and successful business and ServiceNow has been key in all this, so the investment came back to us faster than expected.
