Tip:
Highlight text to annotate it
X
Hello everyone, my name's Richard Sgro and welcome to Localytics' Whiteboard Wednesday.
Today I'm going to talk to you about structuring your organization for mobile success.
Today we're gonna talk about three different organization structures
to help you get
to the mobile goals that you have.
The first model is the one-team model.
In this organizational structure the team that's building core experiences
knows the scenarios best they understand technology and they understand
challenges and the users.
In this model
that team as they finish their core experience, whether on a website or on
a desktop,
they then transition to think about the mobile experience.
Some of the challenges in this model,
first, your team that's building your core experience can often think about
things in one way and think of mobile
as a complimentary or supplementary experience. They may struggle to think about
the mobile first scenario.
In addition,
the skillset thatt your team has in coding, the experience may be on the desktop,
or on the web,
doesn't directly transition to the mobile world.
The second model that we're going to, the second model is
the insourced model.
With this
your core scenario team
is continuing to focus on the core scenario and the core experience.
They build this experience, great, think through all the different scenarios and
angles on the desktop or on the web.
As part of that process they define some mobile scenarios.
As they define those mobile scenarios they work with an internal team of mobile
experts
to get those scenarios developed.
that team is a group of mobile experts and they're thinking about things
always from the mobile angle.
Some of the challenges that exist in this model, first,
collaborating internally in organizations are oftentimes results in
challenges in prioritization.
In addition, that mobile first product team
may have a number of different internal partners, and your scenarios or your
application may not be high on their list so it's important to keep those
things in mind.
The third
and most common model we see is
the outsourced model.
Your team has a great to set of core experiences, they understand the user and
they really want to continue to focus on that.
In the outsourced model the product manager or product owner comes up with the mobile
requirements working with the scenario team,
and he hands those off to an external third-party.
They also hand off some money to the external third-party.
After sometime that external third-party hands back a completed mobile experience.
This is really great if you're looking to get
a mobile experience out the door but there is a cost associated with this
and oftentimes it's higher than the other two.
It's also important to think about
what is the long-term implications of having a external third-party build
an application?
Who owns the bugs if there's an issue found?
Who's going to troubleshoot it, who owns first line support?
So we chatted a little bit about each of these models
and it's important to consider
if your organization, if time is really important you've got a great experience you're
gonna be launching on the web or on the desktop, and you
really need to make sure that you've got a mobile presence,
outsourcing may work really well for you.
If in your organization you've got a
strong group of mobile experts
this insourcing model, perfect for an organization like that, just beware of
the challenges of group collaboration.
If you're fortunate enough to have an organization where you've got
very fungible development team,
I would generally encourage you to think about the one-team model.
This allows your organization to think through all the scenarios from all the
different angles and allows that team to build up great experiences on all the
screens that your experience is going to be on.
So these are the three different organizational models,
I hope you enjoyed our chat today. As I said before my name is Richard Sgro
and this was Localytics Whiteboard Wednesday.
Thank you very much