Sonoma Partners Microsoft CRM and Salesforce Blog

Salesforce1 Mobile – Becoming mobile ready

In my last post on Salesforce1 Mobile I showed you how to brand your mobile deployment of Salesforce1 to better fit your brand’s standards including how to change the logo, colors, and publisher button to your own. Now that you have an application that your users can identify with, it’s time to start thinking about the functionality that will allow your users to be effective and efficient at their daily tasks.

Meet Bob, the sailorman salesman

Let’s meet Bob, a door to door salesman who makes his living selling sailing equipment to private boat owners and retail boat companies. Bob has recently purchased Salesforce to track his various accounts, and is on the road most of the time. To begin, let’s look at one of Bob’s accounts in Salesforce1 mobile, without making any customizations to the forms.


Bob isn’t really happy with this layout. All Bob wants to see is the name of the account, the phone number, and its address (captured in the Shipping Address fields). On the related list page:


Again, there is too much information. All Bob needs is Contacts and Opportunities.

Customizing the forms for the mobile user

Let’s see if we can’t make Bob a little more productive by removing the fields from the form that he doesn’t need. The idea here is that we’re going to create a new form that only contains the information Bob needs to see, and assign it to his profile (Standard User). The other users in the system who do not have the same profile as Bob will continue to see the native form and can continue to use the extra fields if desired.

To create the new form, we go to:

Setup > Customize > Accounts > Page Layouts


On the Account Page Layout page, we’re going to create a new layout - not copying an existing layout - and naming it Standard User Layout.

The new default form includes the required fields by default. Let’s add the fields and related lists Bob wanted to the form.


Clicking Save, we’re brought back to the Account Page Layout page. We need to take one more step before turning this over to Bob – we need to assign the layout to Bob’s profile so that the application will use this new layout instead of the native one when Bob looks at an account.

Click the Page Layout Assignment button and change the Standard User to the Standard User Layout.


Once we let Bob know that the changes are ready and he refreshes the account on his mobile device, he will see the changes:



This is all fine, but we can do better. If Bob clicks the publisher button in the lower right corner, he’s still presented with many options that aren’t relevant to him:



Let’s remove these extra actions to just the ones he needs: new contact, new opportunity and link.

Publisher Actions – Overriding the defaults

Going back to our form, we see the Publisher Actions panel, but it looks like there aren’t any actions! Where are the default actions coming from? 


Reading the text carefully, it’s telling us the layout is inheriting the default ones from the global publisher layout and that we can override it, which is exactly what we’re going to do. Clicking the link provided gives us an editable box where we can drag just the actions we care about.


And back on Bob’s device:



As you can see, enabling users to be productive while in the field is not as simple as giving them mobile access to a desktop oriented site. You need to spend time thinking about, and usually working with, the end user and their day-to-day tasks to customize the experience to best fit their needs. Sometimes this can take many iterations, as the users explore their options. Listen to your users’ feedback, and take it seriously as it may help you improve their efficiency, and by extension the bottom line.

Do you need some help with your mobile strategy? Not sure if mobile is for you? Contact us and we can help – from discovery all the way to delivery and post go-live support.

Topics: Enterprise Mobility Salesforce

When it comes to custom mobile app development, UX matters. A lot.

Sonoma Partners’ executive Jim Steger wrote a post last fall on enterprise mobile applications and their best features. He told an all too true story about his 2-year old’s innate ability to pick up a cell phone and navigate an app like a pro. It’s tempting to say that kids today come out of the womb getting technology these days but the truth is that app developers (the good ones!) just get it.

When it comes to and Microsoft CRM mobile app development, we like to think that our camp of developers “gets it”. We understand that the usability of an app is its most important feature. This is precisely why Sonoma Partners whole-heartedly invests in our mobile app development… instead of just tacking it on to a list of service offerings.


What does this UX investment look like?

Mobile app development comes in a lot of shapes and sizes: a loft space with 50 developers, a guy that remembers “a little code” from his college HTML course, a crowd-sourced app built by amateurs in their spare time, or one well-trained but over-worked developer carrying the entire load.

At Sonoma Partners, we utilize dedicated UX architects on every mobile app development project. At the beginning of your engagement we refer to them as the Silent Observer. They spend a day or two watching your users’ every move (we promise it isn’t as creepy as it sounds) to understand how they truly use your CRM. It would be one thing to interview you and ask you your process but it’s a horse of a different color to watch you use the platform and pick up on the shortcuts you take along the way. The primary goal of our UX architects in this phase is to pick up on your sales staff’s idiosyncrasies to observe and identify where efficiencies can be gained.

What do we do with these observations?

UXblog-smallWe begin an iterative design process. After we synthesize our observations we create low-fidelity mock-ups. We present you with a list of our recommendations and ask you what you think. We want to know:         

  • Have we properly captured how your sales staff uses your CRM on a day-to-day basis?
  • Have we distilled the 4 to 5 things that your users needs to be able to do over and over again with ease?
  • Have we created a dashboard that is easy to use and aesthetically pleasing?

Once we’ve reached an agreement we create high-fidelity mock-ups. This is where your app comes to life with your company’s style guide including logos, colors, fonts and font treatments, and spacing. The mobile app that we create for your CRM or Microsoft CRM platform looks like an extension of your brand.

What do you get?

Assuming we did our jobs right, you’ll get a mobile application intuitive enough to use without any training. Our goal is that you and your sales team should be able to use your mobile application without an instruction manual or lengthy training session. That’s why we invest in UX architects and frontend development. We believe that when it comes to mobile application development, the UX design really matters. A lot.



Topics: Enterprise Mobility

Five Reasons Your CRM Deployment Needs Enterprise Mobility

If you’ve been paying any attention at all to the rapidly changing world of enterprise mobility, you know that if you don’t have a mobile tool you’re already behind. Mobile CRM apps will grow 500% this year and it’s no longer a nice-to-have capability but a sink-or-swim necessity for your sales team.

If you’re still on the fence, or debating whether or not a mobile CRM app is right for you, we’ve outlined 5 essential reasons you need to move mobile to the forefront of your CRM deployment strategy.


#1: You Need to Access Your Data When You Need it

With a solid mobility tool, your sales staff has the ability to access the important information they need at any time. Mobile CRM apps can help your team manage an account from the first moment of contact to the signature on the statement of work.

A mobile application makes preparing for a meeting on the road an effortless activity, allowing your sales team to pull up records and initial communication with a client in one tap. Beyond acting as a valuable resource prior to the meeting, Mobile CRM apps can serve as a presentation tool when you are one-on-one with clients. With your data in the palm of your hand, you have the ability to show your customers the exact products and services you’re selling.

A fundamental goal in implementing a CRM tool in the first place is to capture good data about your customers. Creating a tool that allows your team to enter the details of the meeting and the next steps for a client immediately after the event, ensures that you are receiving the highest quality information. Deploying a mobile CRM application creates the best circumstance for collecting the most accurate data about your potential and existing clients.

#2: You Need to Reinforce Brand Standards

When you’re in the field meeting with a client you want to be able to display your service offerings in a way that will help drive the sale. It’s likely that your customers are peering over your shoulder and looking at the presentation tools you’ve brought along with you. Building a mobile CRM application that is in-line with your brand standards allows you to bring your most powerful sales tool to any meeting, anywhere. Your goal is to delight your customers. One way to do this is to build an application that presents your products and services in the most effective way possible. Use your CRM to facilitate a collaborative conversation about what you have to offer and how you can offer it.

#3: You Need to Put Your Apps Where Your People Are

Do you want your sales team chained to their desk inputting information into your CRM system or do you want them in the field meeting with clients? We’re going to take a wild guess and suggest that you would choose the latter.

Deploying a complex CRM system might work for users sitting in front of their computer all day, but it simply doesn’t translate to your team out in the field. We encourage all of our customers to invest their time and resources into offering a mobile CRM application that allows their sales staff to spend more time selling and less time sitting.

Some businesses think a mobile CRM solution might not work for their users because they don’t always have cellular connectivity. Great news, perpertual data connectivity is not required for businesses to deploy an effective mobile CRM solution. It doesn’t matter if your team is in a basement, a field, or in a building without a solid Wi-Fi connection. Businesses can leverage offline capabilities in a mobile CRM app so that any data updates can be stored offline and will automatically sync when the device finds a connection. With a mobile CRM application you can say goodbye to the “I didn’t have service” excuse forever.

#4: You Need to Acknowledge Different Form Factors and Screen Sizes

DynamicsmobileOn your desktop, you have the screen real estate to perform lots of different actions. You can open multiple windows and drag documents across multiple monitors. When creating a CRM primarily for desktop you have a lot more flexibility on your system design and you might expect a little more effort from your users.

However building a mobile application makes simplifying your system mandatory. Users need to be able to navigate the system in mere inches. This requires that you narrow down your fields and pinpoint the most valuable information. You have to approach the construction of the app from a tappable mindset. What happens when you subtract fields and functionality? You increase the likelihood that your users will adopt the tool.

The less data they are required to collect not only increases adoption rates, but simultaneously increases the likelihood that you will receive the quality data you are looking for.

#5: You Need to Meet Rising Expectations

Remember that statistic projecting mobile CRM growth of 500%? If this enormous number doesn’t get you moving, you can safely assume it will motivate your competitors. And while right now your focus might be on mobile apps for your internal users, you cannot stop there! Everyone - your sales staff, your customers, your prospects, and your leads - expects you to offer mobile capabilities.  We’ve moved beyond the days of printed presentations and product catalogs. Eventually you will need a full-blown mobile experience for each of these different what are you waiting for?!



Topics: Enterprise Mobility

How Medline Leveraged a Custom Mobile App to Achieve Rock Star CRM User Adoption

Medline Industries is a billion dollar equipment manufacturer and leading supplier of medical, surgical and pharmaceutical products to hospitals, nursing homes, HME providers, surgery centers and physician offices. Medline was running Microsoft Dynamics CRM, but unfortunately they were struggling with their prior CRM implementation partner (hey it happens). Their dissatisfaction stemmed from missed deadlines and a lack of recommendations on how to really take advantage of the capabilities that Microsoft Dynamics CRM offers. Consequently, Medline decided to shop around and talk with different CRM implementation partners to see if they could find a better fit.

When Sonoma Partners met with Medline we immediately recognized how important field sales and service was to their sales staff. With 1,500 CRM users spread throughout the United States, the success of their CRM deployment would be directly tied to how effectively their sales team could use CRM on the road.

Prescribing a mobile solution was part of our recommendation from the start. We focused on building a tool that could collect, manage, and store the data that was important to their team and needed to be accessed anywhere at any time. As we layered mobile elements into their CRM we came to the conclusion that constructing and deploying an iPad app would satisfy a majority of their needs.

At the beginning of the mobile project we took the role of silent observers, and spent time with their sales staff in the field to understand their unique user needs. We watched what they did on a day-to-day basis and zeroed in on the five tasks they did over and over again. The five tasks include accounts, contacts, opportunities, notes, and product orders.

Why just five tasks? At Sonoma Partners, we believe that mobile CRM solutions should be built to focus on each user’s most common use cases. If your software can complete the five most important tasks effortlessly, your users are likely to adopt the system and input valuable data every single day. If you make the app anymore complex, you run the risk of your team failing to adopt.

After construction, how did the app perform?

Since deployment, 90% of all opportunities created in their CRM were done through the custom iPad app! This translated to 27,000 records created using their mobile tool in the first few months. Medline’s success story moved from a plotline revolving around a pure CRM to a mobile solution.

The client’s reaction? “This is exactly what we needed.”

If you’re looking for CRM success similar to Medline you need to ask yourself: "Is my sales team on the road most of the time?"

If the answer is yes and you haven’t yet focused your attention on building a mobile tool, it’s time to start.



Topics: CRM Best Practices Enterprise Mobility

DefenseReady Scout Released to the Win 8 App Store!

We are excited to announce the release of the DefenseReady Scout app to the Windows 8 App Store!  This marks the second Windows 8 application deployed to the Windows 8 App Store for Permuta Technologies (DefenseReady Daily Standup being the first)

DefenseReady is a Microsoft Dynamics CRM solution built by Permuta Technologies, Inc. that provides organizations out-of-the-box mission-enabling solutions for Force Readiness, Mission Execution and Training Management.  The Military Services community is a unique community that require immediate insight and control at leadership as well as all functional levels throughout organizations. Leadership needs visibility throughout their organization with minimal impact to operations.

Developed jointly by Sonoma Partners and Permuta, the Scout application was designed for users in the field who gather critical information in support any business activity managed by DefenseReady. Users can leverage the built-in features of their Win 8 devices to generate maps, identify points of contact, collect photos, record audio and capture other types of information. Users can work their Scout Plans, flag items for issue, mark them complete, and when they’re ready they can organize the final data into a brief that can be exported to Microsoft Word and provided to leadership and decision makers.

Scout Event List

When you first log into Scout, you’ll be presented with a list of Scout Events.  These are the high level initiatives for an activity that is taking place. It could be a mission, investigation, emergency response, or any other type of event that requires detail planning.  Each tile displays the start / end date of the event, as well as the number of Scout Plans contained within the event.  From this page a user can create a Brief which we’ll go into more detail on below.



Scout Plan List

When you drill into a Scout Event, you’re taken to the Scout Plan list page.  Scout Plans are broken up by status.  Each tile displays information about the Scout Plan (address, distance from current location, who it’s assigned to, and the percentage complete).  From the Scout Plan page, users can:

  • Select a different Scout Event
  • Add a new Scout Plan (either from a predefined template, or manually created)
  • Lock/Unlock a Scout Plan
  • Create a Brief



Scout Plan Item List

Once you click into a Scout Plan, you’ll see all the Items that make up this plan.  A Scout Plan can have many items that were either manually created, or automatically created from a template (see mini-map section below for more information on the meaning of the icons).  When in the Scout Plan Items list, you can take many different actions by swiping up:

  • Open an Item
  • Mark an Item Complete / Reopen a Complete Item
  • Flag an Issue on an Item / Remove the flag from a Flagged Item
  • Remove / Delete an Item
  • Reorder Items

You can create many different Scout Plan Items within one Scout Plan.  The following item types can be created for any Scout Plan:

  • Voice Memo (using the native microphone capabilities of the device)
  • Image List (using photos existing on the device, or the devices native camera capabilities to take a new photo)
  • Map (using the native GPS capabilities of the device)
  • Free form Text
  • Equipment List
  • Manpower List
  • Risk/Threats List
  • Facilities List
  • Points of Contact List (images saved on the device or new ones taken with the camera can be associated to each contact in the list)
  • Generic Listings



Mini Map

The mini-map appears at the top of the Scout Plan Items list which allows users to quickly navigate between items without having to scroll horizontally through a long list.  Each icon means something different and each Scout Plan Item may have one or more of the following scenarios applied to it (e.g., it can be a Template Item that is Flagged for an Issue but also Complete):

  • Square:  This is an item that came from a template.
  • Circle:  This is a manually created item.
  • Gray Fill:  This indicates the item is still in progress and not complete.
  • Green Fill:  This indicates the item is complete.
  • Yellow Triangle:  This indicates the item has been flagged for an issue to follow up on later.



Snap Mode

Scout utilizes the native Windows 8 experience of being able to Snap an application to a portion of the available screen so allowing users to work within two applications at once.  Scout will resize to the appropriate size and allow you to navigate Scout while also working within the other application.




Scout takes advantage of the power of other already built applications for Windows 8 and integrates that functionality into Scout.  Users can share from the following applications to within a Scout Plan Item allowing users to create this data outside of Scout in a tool they may be more comfortable with using, and at a later time bring it into the app.

  • Skitch –> Scout Plan Item Image
  • OneNote –> Scout Plan Item Text



Generate a Scout Brief

At any point along the process of collecting data and creating a Scout Plan, users of DefenseReady Scout can generate a Brief.  A Brief can be generated either from the Scout Event list, or from the Scout Plan list. A brief can only contain a single Scout Event, but it can contain multiple Scout Plans from that event, as well as multiple Scout Plan Items from the plan(s) selected.

During the brief creation process, a user has the ability to select the Scout Plan(s) to include, the Scout Plan Item(s) to include, and also change the order of where the Scout Plan Items will appear in the generated Word document.  Scout Plan Items default to the order as they were within the plan itself as the user was building it out, but can be changed (only within a single plan – users cannot move items out of one plan and into another for the generated brief).




DefenseReady Scout is currently available for free to users of DefenseReady.  The app also has a built-in Demo Mode.  Therefore, if you’re not currently a DefenseReady customer, you’re still able to download and test it out.  You can currently download the application directly from the Windows 8 App Store, or from this link:

Topics: Enterprise Mobility

Throw Everything You Know About Gathering CRM Requirements Out The Window

I asked a potential client during a recent meeting to describe his method for gathering requirements for his upcoming CRM project. While thumbing through the list of must-haves he gave me, he told me about his round-the-world trip. In order to compile the list of requirements, he flew across several continents to ask members of his sales team: What do you want?

“If I asked people what they wanted, they would have said faster horses.” – Henry Ford

Believe it or not, asking a sales team member what they want is the traditional approach to gathering requirements for CRM systems. If you’re adopting the traditional approach I hate to tell you, you’re doing it all wrong.

When it comes to gathering requirements you can’t ask people what they want, you need to witness what they need. Holding a 60-minute meeting in a conference room isn’t going to give you the meaningful insight you need to build an application that saves your end users time and your company money. If you want to build a CRM application that will ensure user adoption you need to buckle your seat belt and go along for the ride.

The Ultimate Question: Will Our Sales Staff Use It?

RidealongIT and sales professionals know that many CRM systems fail due to poor end user adoption. Therefore if you are making the investment and taking the time to invest in a CRM system…everyone should be laser focused on how to make sure you can achieve high end user adoption. The best way to plan for a high adoption rate is to gather requirements by observing your end users in the field while they conduct their day-to-day tasks.

Decision makers need to put themselves in their sales staff’s shoes (or let Sonoma Partners take the walk for you) and pay attention to their day-to-day activities. The best way to gain insight into these activities is to play the role of the silent observer and spend some time watching. 

What types of things should you be looking for?

  • What are all the various systems and tools the users leverage?
  • What are the data inputs and outputs of each system?
  • Do they have any external files (Excel spreadsheets, Word documents) that they pull out to “really” do their job?
  • What is their hardware situation? How often are they using mobile devices vs desktop/laptops?
  • How often do they connect via wireless versus hard wire?
  • Which web browser are they using?

Really understanding how your sales staff actually gets their job done (instead of how they say they do!) will help you build a CRM system that connects technology with your business process. 

Beware of the Conference Room

Nothing says failure like a plan made in a conference room. It’s easy to hold a brainstorming session and ask attendees to bring a comprehensive list of requirements that they would like to see included in the mobile app.

Unfortunately, what usually comes out of these sessions are unnecessary requests for more: more integrated systems, more data fields, more information, more complexity. We see it often and refer to it as the over-engineering scenario. Clients get tied up thinking about capabilities they may one day want rather than what they need today. What is the result of over-engineering your CRM system? Opportunity, account and contact forms with 150+ data fields each…and none of these data fields will ever get completed!

Our advice? Follow the 80/20 Rule. Focus on the 20% of the information that matters most. Your CRM system will be more valuable if everyone completes the 20% most important data fields, versus having a few users complete 80% of the data. Gathering system requirements by observing end users in the field is the best way to help you identify the 20% of fields your users need to do their job best.

What’s the Objection?

So why do CRM customers still use the traditional approach to gathering CRM requirements? We want to debunk some of the primary objections we hear when trying to convince clients to enlist a silent observer.

  • Our sales staff is too large to get an accurate sample. If your organization has a large sales staff that is spread out geographically, it’s easy to assume that getting an accurate sample size is impossible. The truth is you don’t need to interview everyone to get a clear idea of how your staff uses your CRM. In our experience we find that a handful (yes, that’s about 4) of observations can shed light on the prevailing trends your staff faces. 

  • Our sales staff doesn’t know what they want. We hear this a lot from IT departments. Traditionally IT plays a leading role in CRM software selection even though they never touch the final product. You need to internally remove this stigma and trust that your sales team not only knows what they want, but has an idea of how the technology can improve the way they work.  

If you’re ready to toss the traditional method out the window, our skilled user experience architects are ready to pull up a chair and observe. We’re here to help and build a CRM application that will positively impact your workforce and your bottom-line. 



Topics: CRM Platform Selection Enterprise Mobility

What is your enterprise mobile application 'Best At'?

Have you noticed a child using an app (usually a game) on a mobile device? Regardless of the device, my children (even as young as 2) have no trouble finding the games that interest them, understanding the device’s gestures and have yet to read a manual to play. They quickly become proficient at the applications that interest them. Part of the reason is the applications themselves are specific, use visual design techniques and contextual walkthroughs to guide the user (in this case my children).

multiple mobile device img

With the recent emphasis of enterprise mobility, many organizations are looking at how to best get started in this growing space. Some look to what devices they should support, others start with architecture and technical discussions or with what applications should be consumed on this new technology. I have found that the most impactful approach is to first ask the question 'what should my mobile application be best at'? Forgiving the fact I ended a sentence with a preposition, to me this question sums up where you should concentrate your initial effort, not on the technology, architecture or even device.

We take a targeted, user-intuitive approach with business applications. At Sonoma, we created an entire team specifically around user experience, design, and mobile development. Our team focuses on these guiding principles when addressing our enterprise mobile application projects:

  • Focus on a discrete use case
  • Understand your user and make the application relevant to them
  • Keep it simple
  • Design first
  • Reflect your organization’s brand

In order to distill the complexities of business processes to a series of screens or events suitable for a mobile device, we first start with the use case or user process we would like to enable. From there, we determine what does the application need to be ‘Best At’? Once this foundation is in place, we derive the solution architecture, device strategy and the remaining logistics to deliver an impactful mobile application to your users.


Are you not sure how to get started with enterprise mobility? Consider trying our Mobility Test Drive experience and let us help you find what your mobile application needs to be 'Best At'.

Topics: Enterprise Mobility

What's New in Microsoft Dynamics CRM 2013 For End-Users: Native Mobile Apps

Today's guest blogger is Jacob Cynamon-Murphy, a Sales Engineer at Sonoma Partners

End-users want CRM to work wherever they are, whether on a desktop, laptop or mobile device.  In the past, Microsoft has addressed this demand with the Mobile Express product.  With the launch of Dynamics CRM 2013, end-users now have a rich tablet application that provides dashboards, charts, and CRM record access from iPads and Windows 8 tablets, enriching the mobile user's experience and productivity.

By simply downloading an app from the App Store or the Windows Store, tablet users can unlock a consistent, intuitive experience like that of Dynamics CRM in the browser. No longer do road warriors need to be tied to a desk to be productive; Microsoft has provided CRM on the go, so mobile users can now touch, tap, and swipe their way to record sales and service results.

Enjoy the video preview of this great new mobile application!


Topics: Enterprise Mobility Microsoft Dynamics CRM 2013

Drive More Business With Mobility

Today’s guest blogger is Kyle Gerstner, a Principal Mobility Architect at Sonoma Partners.

When you hear iPad, Surface, Droid Tablet, what do you think about?  Shooting birds at pigs, slicing fruit, checking Facebook/Twitter/Instagram?  We have been trained to think of these mobile devices as consumer products intended for fun, but its time to start thinking of how to leverage them for business.

Every company knows that in order to be successful, they need to make the right decisions; and in order to make those decisions, they need data.  Companies have spent thousands if not millions of dollars on complex systems that allow you to enter in your data and then report on that data, see charts, and help make decisions.  These tools can be customized to fit your exact business process, which makes them excellent for your analysts and decision makers.  Analysts are noticing a new problem; there isn't enough data?  Why?

Unfortunately, the highly customizable systems quickly become too complex for the people who need to fill in that data.  The people that make up the public facing side of your company: sales people, support staff and anyone else who interacts with your customers.  These are the people who have their own system of tracking the data that is important to them.  They use notebooks, napkins, or sometimes, just their memory.  A lot of these people become overwhelmed by these complex backend systems and when it doesn't work the way the expect/want, regress to their system of napkins.

A mobile application allows you to present a streamlined interface to your complex backend systems.  In fact, a well designed application means your users don't even have to know what that backed system is!  In my experience, most users in the same role follow roughly the same set of steps when they meet with a customer.  If you provide an intuitive interface that walks the user through those steps, gathering the data your company needs along the way, and sending that data back into your system, everyone wins.  Your employees will be happier because they can ditch their notebooks and carry a tablet.  The company will be happy because you'll have more and better data entered into your system, which allows you to make better decisions.

A key point here is a streamlined interface.  A mobile app should not be all encompassing.  It should be focused on a key set of use cases and make that experience the best possible experience for the user.  There will be cases where the user will have to break out the laptop either right away or at the end of the day to deal with a unique circumstance that isn't covered in the app.  Also, you don't have to hit all possible use cases in the first iteration. Many successful applications I've built have had second and third iterations defined by the users, and what they feel they need. When a company allows their user base to drive the feature set of the application, they see an increase in adoption.

It's time to stop thinking about mobile devices as toys and start thinking of how you can leverage them to build your business.


Topics: Enterprise Mobility