Blogs LHC

Blog - Prime Content

Affino and the Art of Phasing

Affino Unified Digital Business PlatformDigital Business DevelopmentDigital Business PlatformImplementation ProcessPhases of ImplementationSite Launch+-

When implementing an Affino Digital Business Solution, you need to have clear goals in mind before you settle on the final configuration. No matter what you select, there will always be follow-on phases to the project, as everything can of course be improved upon and refined.

The huge scope and scale of Affino is such that it would take a very significant time if you wanted to make use of every single element of functionality on offer. That said, when most Clients get into Affino, they almost always want to add more elements which are outside the original scope and proposal.

There is often not sufficient consideration as to the impact of front-loading more features and functions, as this almost without exception will impact on timelines and costings. And it is rarely a case of sacrificing a little bit of something agreed for something slightly different. All additions have knock-on effects in one way or another, and some of the seemingly smallest ones can be the most significant.

There are of course some business-model reasons why it may make perfectly good sense to make alterations to scope. But a lot of the time it is more of a case of simply having more bells and whistles at launch. Throughout the process you must consider the most typical end-user / consumer, and gauge how receptive they will be of the overall solution. Too much too soon is not always a good thing. It goes without saying that the core functionality should be in place. But it is usually a much more successful policy to phase in new features and functionality on a more extended timescale - and within some sort of environment of co-operaiton and consultation.

I have evolved some helpful rationale for assisting in some of the key decisions:

Dates vs Contingency

Probably a greater number of projects have seemingly unmovable target dates which don’t adequately make room for contingencies - which become more important, the bigger and more complex the project becomes. When you are doing something new - which most digital business deployments tend to be - you are rarely just copying exactly the same template and running with all the same settings and tolerances. In most instances inadequate planning consideration is given to full testing and soft-launching. If the date is totally hard and fast, then there has to be some flexibility in the scope - in terms of the usual PQT triangle dynamics. As almost without exception new evidence arises during implementation and testing which results in some degree of change of plan - which in turn means more time will need to be spent in certain areas. With complex systems there is often a further knock-on effect which means redevelopment / optimisation of other essential components is required. So as every single development manual warns and advises you will usually have to make some concession to what is developed and for when.

Essentials vs Nice to Have

When you launch your new solution the essentials have to be in place to make the business work, often you also need specific differentials to set you apart from your competition. And these together are everything that needs to be ready for launch. There are then a load of Nice-to-haves - which add a little extra value and quality, but are quite obviously not needed for the business to work successfully. People often get hung up on all the Nice-to-Haves which delays the launch of the business - where you could have been making money / more money already.

Soft Launch vs Big Bang

It is almost always in your best interests to engage in a soft launch - i.e. trial the site with a smallish but representative group of customers for a few weeks - before you launch to everyone. No matter how much testing you do, there will be some issues that only materialise when real customers are using the site. Those that do hard launches often experience unnecessary stress in dealing with high-pressure issues - which would have been far more manageable in a more controlled soft-launch operation.

Rapid Release vs Consultation / Suggestion Box

Experience tells us it is best to work in consultation with the end-users. Give them a voice in the development of the service and they are more likely to become loyal advocates. There are good and bad ways to go about this - do not have a negative stance in terms of getting people to report what’s wrong. Instead have a feature request area / form or some sort of suggestion box for users / consumers to recommend useful updates. You can even offer some sort of relevant reward - extended membership etc. for good ideas. This can also be used strategically to find support and endorsees for new innovations and forthcoming changes to the service. As always we encourage Affino site owners to be aware of vocal minorities and silent majorities when dealing with certain issues - you always need a critical mass of consensus to get a proper gauge of where your customers mindset is at. We also advocate structured 6 month / 12 month updates as too much chopping and changing can be discouraging and disorienting for consumers.

Bedding-In vs Knee-Jerk

Everything takes a while to settle in or settle down. Whether a new car or new musical instrument, they need to be broken in to a degree before you can take a proper status on how smoothly they are operating, The same is the case with digital business solutions. We’re not meaning bugs and glitches here - as for sure those will need to be ironed out as soon as possible. What matters here is the processes and workflows - whether these are working optimally, whether everything is easily learnable and suitably user-friendly. When you present anything new, you always get a load of kickback from certain types of individuals. We encourage you by all means to take note of the feedback, but bide your time and take a circumspect view on proceedings. You will rarely please all of your customers all of the time, so it is important that the vast majority are suitably satisfied. There will always be complainers and disruptors, and you will need processes for dealing with them. You most be responsive in communications, set out your direction clearly, but not necessarily act on something which may be a vocal minority view.

Short Term vs Long Term

An original Affino site implementation takes anything from a few weeks up to around 18 months for the more complicated builds - usually conditional on how much of the required functionality is entirely new. The short term timespan depends also as much on the degree of complexity of build and size of solution - so mileage can vary significantly. We do encourage more longer-term strategic thinking with clear milestones at annual or six-monthly intervals. It makes sense for some to be on a quarterly basis, but doing monthly updates is probably too much, as every new introduction takes a while to bed in, and will have some unforeseen knock-on effects which may take some time to smooth out. Like with Apple, customers like to know there are regular updates and innovations, but too many of these and it becomes a negative, a disruption and an inconvenience.

Launch vs Phase 2

This is probably the biggest area for headaches for both us and our Clients - and always involves additional features and functions identified during the process of implementation. The fact is that there will always be a phase two, various aspects of an implementation can always be improved during a review and various behaviours come up only when the site has been fully in Live mode for a while. There is the question of opportunity cost in launching the site later versus the opportunity cost of launching something perceived incomplete or nonoptimal. Change requests themselves can be quite messy, and a seemingly small adjustment may mean quite significant additional development work. So it’s back to reviewing the PQT triangle in terms of discerning where you should draw the line in the sand. There has never been a 100% perfect launch, in much the same way that pretty much every printed work out there, no matter how often reviewed normally has at least a handful of mistakes - typographical, spelling or grammatical. The more user data you have, the better you are able to make your solution - which means usually the solution being active in the real world and dealing with wholly real-world scenarios. Some of your perceptions may be proved wrong, so it is often in your best interests to keep a certain amount of tasks in reserve for phase 2 - depending on feedback and outcome of the actual launch...

Legal

Cookie Settings

Custom ID

Privacy Preferences

Your Privacy

Strictly Necessary Cookies

Performance Cookies

More Information

What are Cookies?

Cookies are tiny text files that are placed on your computer, mobile phone, or other device, and help provide you with the best experience we can. They are used by most websites to help personalise your web experience. Some features will not function if you do not allow cookies.

Our cookies help us:

Make our website work as you’d expectSave you having to login every time you visit the siteRemember your settings during and between visitsImprove the speed/security of the siteAllow you to share pages with social networks like TwitterContinuously improve our website for youGranting us permission to use cookies

If the settings on your software that you are using to view this website (your browser) are adjusted to accept cookies we take this, and your continued use of our website, to mean that you are fine with this. Should you wish to remove or not use cookies from our site you can remove them, however doing so will likely mean that our site will not work as you would expect.

It is only once you sign up and provide consent that the system will look to personalise the experience for you with best matching content and other recommendations.

Which cookies do we use and why?

Across the site we use the minimum number of cookies, with no third party analytics tracking, e.g. Google Analytics. There are however some key social, audio and video embeds which are used on the site and these in turn use cookies, we recommend that you use privacy and ad blocking plugins to minimise the number of third party cookies, none of which are required for affino.com.

1. Strictly necessary

Strictly necessary cookies are essential in helping you to move around our websites and use their features, such as accessing secure areas of the website and shopping. These cookies don’t gather any information about you that could be used for marketing or remembering where you’ve been on the internet.

We use these Strictly Necessary cookies to:

Remember things like information you’ve entered on order forms when you navigate to different pages in a single web browser sessionRemember the goods and services you ordered when you get to the checkout pageIdentifying you as being signed in and keeping you logged in throughout your visit so that you don’t need to sign in each and every time you visit.Using our site indicates that you accept the use of ’Strictly Necessary’ cookies.

Accepting these cookies is a condition of using the website, so if you prevent them we cannot guarantee how our site will perform for you.

Here is a list of the cookies we have defined as ’Strictly Necessary’

Host: affino.comCookie names: JSESSIONIDPurpose: To keep track of user sessions on the site and identify your user session on the server level.

These cookies allow websites and applications to remember choices you make (such as your user name, language or the region you are in) and provide enhanced, more personal features. They do not gather any information about you that could be used for selling advertising or remembering where you’ve been on the internet, but do help with serving advertising.

Some examples of how we do this include:

Remembering your preferences and settings.Show you when you’re logged in to the websiteSupporting social media components, like Facebook or Twitter (where a website uses a plugin from these third party platforms, for example).Remembering if you’ve been to the site before so that messages intended for first-time users are not displayed to you.Remembering your search settingsMaking our shopping basket and checkout workRemembering if you have accepted our terms and conditionsUsing our site indicates that you accept the use of ’Functional’ cookies.

Accepting these cookies is a condition of using the website, so if you prevent them we cannot guarantee how our site will perform for you.

Here is a list of the cookies we have defined as ’Functional’:

None

3. Performance (analytical)

’Performance’ cookies collect information about how you use our website e.g. which pages you visit, and if you experience any errors. These cookies don’t collect any information that could identify you - all the information collected is anonymous and is only used to help us improve how our website works.

Some examples of how we do this include:

Provide statistics on how our website is usedSee how effective our adverts are (we don’t use this information to target adverts to you when you visit other websites)Provide feedback to partners that one of our visitors also visited their website. This can include details of any products bought. This lets our partners improve their website, but we don’t allow our partners to reuse this information for further advertisingHelp us improve the website by measuring any errors that occurUsing our site indicates that you accept the use of ’Performance’ cookies.

Accepting these cookies is a condition of using the website, so if you prevent them we cannot guarantee how our site will perform for you.

Here is a list of the cookies we have defined as ’Performance’:

None

4. Target or Advertising (3rd party)

’Targeting’ cookies are linked to services provided by third parties, such as ’Like’ buttons and ’Share’ buttons. The third party provides these services in return for recognising that you have visited our website.

An example of this includes:

Link to social networks like Facebook, who may subsequently use information about your visit to target advertising to you on other websitesWe use third party services provided by third parties like YouTube or Vimeo who may subsequently use information about your visit to target advertising to you on other websitesYou can control whether or not these cookies are used, but preventing them may stop us from offering you some services. All of these cookies are managed by third parties, and you may alternatively use the third parties’ own tools to prevent these cookies.

Here is a list of the cookies we have defined as ’Targeting’.

None

Third Party Cookies

Some third party content may be embedded in pages on Affino.com and these may have the ability to track and personalise your experience for the embedded content. Examples of third party cookies are:

Host: soundcloud.comCookie name: __utma, __utmb, __utmc, __utmzPurpose: Soundcloud can be used to share music and audio files. They use google analytics to capture visitor information

Host: youtube.comCookie name: PREF, use_hitbox, PRVISITOR_INFO1_LIVEEFPurpose: When you view a web page on your site with an embedded YouTube video, YouTube creates these cookies

Host: twitter.comCookie name: personalization_idPurpose: When you view a web page on your site with an embedded Twitter card, Twitter creates this cookie.

How you can control cookies

1. Browser controls

Most modern browsers offer you ways to control or block cookies. These browser controls will usually be found in the “options’ or “preferences” menu. For more help, you may take a look at the “Help” settings or review these website for more details - http://www.aboutcookies.org/Default.aspx?page=1

2. Ad cookies and targeting

You can find more information or turn off targeting by member companies at YourOnlineChoices UK http://www.youronlinechoices.com/uk.

About this policy

If our use of cookies changes, we will post the changes to this policy. Please check frequently as online data collection practices and our use of them continue to evolve. To contact us about this policy, you may email support@affino.com

This version of the privacy policy is effective as of Aug 1 2018

Strictly Necessary Cookies

Strictly necessary cookies are essential in helping you to move around our websites and use their features, such as accessing secure areas of the website and shopping. These cookies don't gather any information about you that could be used for marketing or remembering where you've been on the internet.

We use these Strictly Necessary cookies to:

Remember things like information you've entered on order forms when you navigate to different pages in a single web browser session

Remember the goods and services you ordered when you get to the checkout page

Identifying you as being signed in and keeping you logged in throughout your visit so that you don't need to sign in each and every time you visit.

Using our site indicates that you accept the use of 'Strictly Necessary' cookies.

Accepting these cookies is a condition of using the website, so if you prevent them we cannot guarantee how our site will perform for you.

'Performance' cookies collect information about how you use our website e.g. which pages you visit, and if you experience any errors. These cookies don't collect any information that could identify you - all the information collected is anonymous and is only used to help us improve how our website works.

Some examples of how we do this include:

Provide statistics on how our website is used

See how effective our adverts are (we don't use this information to target adverts to you when you visit other websites)

Provide feedback to partners that one of our visitors also visited their website. This can include details of any products bought. This lets our partners improve their website, but we don't allow our partners to reuse this information for further advertising