David Pemsel, deputy chief executive of Guardian News & Media, recently gave a short speech about the organisation’s strategy.
[You can watch the speech below (or read highlights here):]
As Pemsel says, what they are doing goes against all conventional wisdom. But readership and revenues are growing, and previous posts (on readers and advertisers) have shown how this makes complete sense when considered through the lens of The Escher Cycle.
This third and final post looks at the big picture: what David calls “the ecology of news provision”.
It examines The Guardian’s role within that space, by applying the thinking of chapter 7 of The Escher Cycle. Continue Reading >
David Pemsel, Deputy chief executive of Guardian News & Media, recently gave a short speech about the organisation’s strategy. You can listen to that speech here (highlights below):
As he says, what they are doing seems at first glance to be crazy. Giving content away for free goes against all traditional wisdom about what it takes to run a successful newspaper.
Seen through the eyes of received industry thinking their strategy doesn’t make sense.
But seen through the lens of The Escher Cycle it is very easy to understand what they are doing and why.
Our previous post looked at how giving content away for free is part of their strategy to ‘grow, deepen and retain’ relationships with readers/members. This is about applying The Escher Cycle’s ‘Customer Chain’ thinking (chapter 2).
This post looks at the changing relationships with advertisers, using the ‘Audio cycle’ thinking of Chapter 6 and the ‘fractal economy’ thinking of Chapter 7.
A third post looks at the implications for the company’s future deep strategy and the evolution of human culture.Continue Reading >
The only cookies we use are Wordpress and Google cookies that are functionally necessary to make the site work and to track anonymous visitor data. We cannot turn them off. By using our site, you consent to these cookies.
Cookie Preferences
Manage your cookie preferences below:
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
You can find more information in our Cookie Policy and .