Marketing Harmony

Older Adults Flocking to Social Media

(download)

senior.jpeg

From the Pew Research Center:

While social media use has grown dramatically across all age groups, older users have been especially enthusiastic over the past year about embracing new networking tools. Social networking use among internet users ages 50 and older nearly doubled—from 22% in April 2009 to 42% in May 2010.

  • Between April 2009 and May 2010, social networking use among internet users ages 50-64 grew by 88%--from 25% to 47%.
  • During the same period, use among those ages 65 and older grew 100%--from 13% to 26%.
  • By comparison, social networking use among users ages 18-29 grew by 13%—from 76% to 86%.

“Young adults continue to be the heaviest users of social media, but their growth pales in comparison with recent gains made by older users,” explains Mary Madden, Senior Research Specialist and author of the report. “Email is still the primary way that older users maintain contact with friends, families and colleagues, but many older users now rely on social network platforms to help manage their daily communications.”

  • One in five (20%) online adults ages 50-64 say they use social networking sites on a typical day, up from 10% one year ago.
  • Among adults ages 65 and older, 13% log on to social networking sites on a typical day, compared with just 4% who did so in 2009.
  • At the same time, the use of status update services like Twitter has also grown—particularly among those ages 50-64. One in ten internet users ages 50 and older now say they use Twitter or another service to share updates about themselves or see updates about others.

  • Posted

    @fredwilson gives a shout out to @nwc

    The "grandaddy" of NYC coworking spaces is New Work City. They just raised almost $20k on Kickstarter to open "the awseomest coworking space NYC has ever seen."

    Very cool. Props to my man @tonybgoode.

    Posted

    Great design can impact even mundane items: Unusual Shopping bags

    These photos are from a post by Clementine, who has a brilliant eye for design.  These struck me not only for the sheer creativity they represent, but that they were working with everyday objects that most people don't give a second thought to.  This is something that we Marketeers need to keep in mind:  

    There is no item too small or meaningless to not warrant our attention. 

    Everything we touch should represent The Brand.  Every nook and cranny of The Brand is an opportunity to make an impression.

               
    Click here to download:
    Great_design_can_impact_even_m.zip (366 KB)

    Posted

    ECKMA: Foolproof way to Get Things Done

    We all suffer from opportunity overload.  Phone calls, Twitter, Buzz, Blogs, RSS Feeds - there is so much to keep up with that sometimes it seems difficult to find the time to do some real work.  You know what I'm talking about.

    Let me introduce you to a simple technique for getting to the Things That Need To Get Done: 

    ECKMA - Everybody Can Kiss My Ass

    I came across this in a post by Adam Rafferty, a brilliant guitarist that I follow, who was talking about how he makes time for his music.

    If you don’t take a stance to work on your craft daily, all the social media in the world means little. You and only you can put the balance in your life.

    You have to do

    - your own pushups
    - your own songwriting
    - your own practicing
    - your own inner spritual work

    …as well as your marketing. But don’t forget about your craft.

    And this means TURNING OFF the computer, the iPhone, the TV and giving yourself the essential gift of silence, time and the joy of creation. Everyday you should unplug for a chunk of time.

    He is talking about the craft of music making, but he could be talking about the craft of the Marketer as well.  You need some some space to be creative - and what we do IS creative.  Silence and Solitude are the best environment for creative work.  Unplug and focus.

    Good luck. It's a noisy world out there. 
    Posted

    "When I die I want to come back as me": Marc Cuban Unabashed Interview

    Posted

    Social Profile Interactive Tool

    Posted

    From requirements to delivery. The old game of Post Office played out in product delivery.

    Posted

    Creating a loved brand by telling a story: Tether

    Excellent interview by Robert Scoble of uber-designer Stanley Hainsworth. I particularly like the focus on telling stories. "All companies have stories."

    And Dude, where DID you get that hair?!

    Posted

    @Apstrata has a unique offer for web developers

    I am working on a couple of web apps that are in the early phase of the life cycle.  We are in the PRD/Architecture phase, so we have not started to code yet.  Both apps have some functional requirements that are similar to many web apps:
    • User/Group management with permissions-based access to data
    • Secure and persistent data store - preferably no-sql
    • Cloud-based and horizontally scalable
    • Server-side processing accessible by client via RESTful API
    In addition, one of the apps had some specific requirements for:
    • storing multiple file types
    • versioning
    • full text search
    • encryption
    These basic requirements probably fit most new web apps as they are being developed.  Nothing new and ground-breaking, so we looked at the usual suspects for providing the application infrastructure:  Amazon Web Services and Google App Engine.

    AWS

    AWS is the big dog on the block and they have they most wide array of virtualized infrastructure.  We looked at a simple architecture such as this:


    This is a lot of components to manage and write software for.  Pretty much the same, from a software perspective, as building a dedicated hosted solution.  We needed to add all the server-side logic for processing the data and storing it.  And we had to develop our own User Management system.

    Google AppEngine

    Next we looked at Google AppEngine.  This was a lot closer to what we needed.  Rather than just virtualizing the hardware components in a 3-tiered architecture as AWS does, Google AppEngine provides a higher level of abstraction.  We don't need to worry about machine instances with Google AppEngine because they take care of all the scaling issues.  But there were quirks that made it less than perfect for our needs:
    • The User Management that comes with AppEngine requires Google Accounts.  That would not work for our app so we still needed to develop our own user management system.
    • Much of the file manipulation that we needed - except for search, of course, still needed to be coded by us.

    We probably would have decided on Google AppEngine had I not been familiar with the Apstrata service.  Full disclosure:  Apstrata is one of Consensio's clients.  I was not bound to use Apstrata in these projects because of our existing relationship - the working paradigm was to pick the best technology - but we took a look for completeness.  We were very pleased to see that almost all of our server-side requirements are met by Apstrata out-of-the-box. Apstrata's basic API offers:
    • Document-style, no-sql database
    • versioning
    • full text search
    • User management with ACL-based permissions
    • RESTful API with Javascript support
    • Server-side scripting for managing complex actions
    • Horizontal scalability provided as part of the service
    Conclusion

    We are going to use the Apstrata service because it makes our life much easier and allows us to get to market more quickly and reliably than if we had to roll our own.  I am impressed (again) with the breadth of the functionality that Apstrata offers and this allows us to focus on the User Experience - which is our real value add in these projects.

    Apstrata has a hard time getting noticed in the shadow of AWS and Google (and Rackspace and Salesforce.com) - but this unique service is something that all web developers should at least review prior to making final architecture/design decisions.
    Posted

    @Apstrata has a unique offer for web developers

    I am working on a couple of web apps that are in the early phase of the life cycle.  We are in the PRD/Architecture phase, so we have not started to code yet.  Both apps have some functional requirements that are similar to many web apps:
    • User/Group management with permissions-based access to data
    • Secure and persistent data store - preferably no-sql
    • Cloud-based and horizontally scalable
    • Server-side processing accessible by client via RESTful API
    In addition, one of the apps had some specific requirements for:
    • storing multiple file types
    • versioning
    • full text search
    • encryption
    These basic requirements probably fit most new web apps as they are being developed.  Nothing new and ground-breaking, so we looked at the usual suspects for providing the application infrastructure:  Amazon Web Services and Google App Engine.

    AWS

    AWS is the big dog on the block and they have they most wide array of virtualized infrastructure.  We looked at a simple architecture such as this:


    This is a lot of components to manage and write software for.  Pretty much the same, from a software perspective, as building a dedicated hosted solution.  We needed to add all the server-side logic for processing the data and storing it.  And we had to develop our own User Management system.

    Google AppEngine

    Next we looked at Google AppEngine.  This was a lot closer to what we needed.  Rather than just virtualizing the hardware components in a 3-tiered architecture as AWS does, Google AppEngine provides a higher level of abstraction.  We don't need to worry about machine instances with Google AppEngine because they take care of all the scaling issues.  But there were quirks that made it less than perfect for our needs:
    • The User Management that comes with AppEngine requires Google Accounts.  That would not work for our app so we still needed to develop our own user management system.
    • Much of the file manipulation that we needed - except for search, of course, still needed to be coded by us.

    We probably would have decided on Google AppEngine had I not been familiar with the Apstrata service.  Full disclosure:  Apstrata is one of Consensio's clients.  I was not bound to use Apstrata in these projects because of our existing relationship - the working paradigm was to pick the best technology - but we took a look for completeness.  We were very pleased to see that almost all of our server-side requirements are met by Apstrata out-of-the-box. Apstrata's basic API offers:
    • Document-style, no-sql database
    • versioning
    • full text search
    • User management with ACL-based permissions
    • RESTful API with Javascript support
    • Server-side scripting for managing complex actions
    • Horizontal scalability provided as part of the service
    Conclusion

    We are going to use the Apstrata service because it makes our life much easier and allows us to get to market more quickly and reliably than if we had to roll our own.  I am impressed (again) with the breadth of the functionality that Apstrata offers and this allows us to focus on the User Experience - which is our real value add in these projects.

    Apstrata has a hard time getting noticed in the shadow of AWS and Google (and Rackspace and Salesforce.com) - but this unique service is something that all web developers should at least review prior to making final architecture/design decisions.
    Posted