One ERP programme per issue, laid out for the people who sign for it
Each issue of the brief takes one stopped programme or one go-live and lays out what was reported, what the reports cannot tell you, and what a steering committee can ask each quarter. Issue 01 is the Zeiss SAP case, and it is on the site. People who join before membership opens are founding readers and hear about it first.
Get issue 01: the Zeiss case, for a steering committee
One ERP programme per issue, for the people who run and sign for it. Issue 01 is the Zeiss case.
What is in an issue
- The reported record
- What the named outlets reported, in order, each line linked to its source, with the company's response where the source has one.
- The timeline
- The dates on one table, with who reported each one.
- What the issue cannot establish
- Where the public record stops, stated plainly, so nobody takes a question for a finding.
- The committee paper
- The working half: three numbers to ask for, six questions for your own programme, and a page you can print. See it in issue 01
Fair questions
I already follow the page on LinkedIn. Why the email?
The LinkedIn page carries the daily news. The brief takes one programme per issue and sets it out for a steering committee. New issues appear on the site first, at /brief/.
Who is it written for?
CIOs, CFOs, programme directors and the architects and consultants who work for them. They sit in steering committees, or prepare the papers for one.
Do vendors pay to be in it?
An issue can carry one sponsor slot, and it is labelled. Sponsors never see or shape the stories. How we work.
What does it cost?
Nothing today. Later there will be a paid membership with the full playbook archive. Founding readers hear about it first. Membership, before the price
P.S. Our Zeiss story reached 256,159 LinkedIn impressions and 249 comments. Issue 01 puts the reported record and the committee questions on one page.
Get issue 01