Site Loading...
Your address will show here +12 34 56 78
Product Management
In short, yes. These days the internet is accessed through a plethora of devices: desktop, laptop, tablet, mobile and even smart watch. So what do you do when it comes to designing your website and which device do you design for? The majority of internet traffic is migrating towards tablet and mobile – Facebook apparently has more than 70% of its access from mobile devices – so you need to design for them all, and the only way to successfully do that is to design responsively.  

1. Start with the user and the content
Content, content, content. Who are you building the site for and what types of content do they expect to see? How are you planning on connecting your content so that your user can find more content that is relevant to their needs? Think about the types of use cases that will be involved and what that means for your content length, style and tone.  

2. Make the decision to design responsively, not adaptively
True responsive design continues to change even after the page has loaded – unlike adaptive which loads the size of page most suitable for the device size it believes you are on. You can see this in action by dragging your browser window to make it bigger and smaller – if the site resizes, it’s responsive; if it doesn’t, it’s adaptive.  

3. Mobile First
Do the most difficult thing first, so now that you’ve established your content hierarchy, work out how that’s going to fit on the smallest possible screen size. What will it look like? Is it logical? Will someone be able to use it while they walk? Crack the mobile layout and the others will flow way more easily.  

4. Test and Roll
This should really go without saying, but make sure you’re testing your design, not just for functionality, but for usability. Don’t design for an end state that a user might not want. Technology moves too quickly now to do end state designs for every screen of a site, so do the design as part of an agile development process. You’ll thank me later.  

5. Make sure your designers and developers communicate constantly
A great design is fabulous, but if the effort to do that outweighs the business value associated with that feature then you need to revise the design – and vice versa. If the feature has masses of business value, make sure you tell the designers so that they can spend a bit of extra time on it.
0

Emerging Technology in Advertising, Mobile Apps, Mobile Optimisation, Product Management
A study from eMarketer notes that adverts on mobile web gets considerably more click throughs than adverts displayed via mobile apps. It’s a fairly significant difference, with 35% on mobile web, and 26% on mobile apps. So what does that mean for publishers who run an advertising model? Likely that it’s time to pursue a two pronged strategy similar to the one that the New York Times has been attempting.

Give those customers who are new and find you via search, Facebook and other social channels access on the mobile web with ads and native sponsored content and focus the effort on developing apps which are single purpose and not free to download – similar to the New York Times Now app which is $6 per month and gives users a summarized version of the top stories from NYT.

These apps should be directed towards your loyal customers, who are coming to you because of the types of content you provide and the brand recognition you have built up. Key to this strategy is remembering the different use cases that your customers have on mobile, and then the difference use case between mobile web (often a push scenario which is more transient) and apps (a pull scenario which is more consistent). Monitor your results, and in true agile style – inspect and adapt.
0

Product Management
We recently launched a new product into the Apple App Store and it reiterated to us 5 key things to remember when embarking upon a product launch.

1. Test, Test, and Test Again
There is no substitution for thorough testing, and the more devices and operating systems you do it across the better. What appears to work and look good on one device will not necessarily work on another, and vice versa. Get yourself a proper test plan, and detail out all your test cases to make sure you’ve got a record of the testing you’ve done, and can provide your developers with as much information as possible to help reproduce any issues that you find.

2. Immerse yourself in your audience
Find out as much as you can about your target audience, their practises and how they use technology in order to mould your product launch into a language they understand, at a time and place which is convenient to them.

3. Stay on Top of your Statistics
If you already have a version of the product in market, keep an eye on your statistics to see when the product has the least usage so that you can launch your new version in the time with the least traffic. This decreases the impact you’ll have on your users if anything goes wrong, and you have to rollback.

4. Always have a rollback plan
No matter how perfect your new product seems in testing, there is no telling the variables that can change and what will happen when you go live. This means you need a rollback plan. What you will do in the event of having to remove the latest update to your product and how you plan to migrate users back to the old version.

5. DVT 
Not Deep Vein Thrombosis, but your Deployment Verification Testing. When all your scripts have been run, and your production release checklist is complete, it’s time to check what your release looks like in production. Don’t ever forget this one, as things have a habit of changing in live environments.
0

Product Management
We came across this post a week or so ago and decided we’d re-post it since we think it gives a pretty good description of what product management is, why you need product management in your business and what a product manager does on a day to day basis.

We’re always being asked by friends and family alike just what being a “product manager” really means and it’s confusing for them because we don’t work with physical product but we manage digital products. As this article points out, some organisations have many people doing different facets of the role, but that’s a mistake.

You need one individual who owns the entire product vision and is therefore able to see the macro, whilst being deep down in the micro detail. An individual who is market facing, whilst customer centric. An individual who is as involved with sales as they are with tech. Basically an oxymoron.

It’s a long article, but a great read and you should definitely persevere until the end.
0

NO OLD POSTSPage 2 of 2NEXT POSTS

Link partner: slot5000 luxury333 batman138 dewagg idngg vegas88 elanggame bro138 bos88 gen777 zeus slot roma77 liveslot168 luck365 sky77 maxiwn138 harta138 qq1221 qqdewa qqalfa qqpulsa qq88asia qqslot777 roma77 pg slot habanero slot mahjong slot