• Home
  • About
  • The Good Strategy Blog
  • Strategy
    • Data Warehousing
    • Ask Martyn

GOOD STRATEGY

~ for every significant challenge

GOOD STRATEGY

Tag Archives: Data Warehouse

Consider this: Big Data Inertia

22 Tuesday Mar 2016

Posted by Martyn Jones in 4th generation Data Warehousing, All Data, Big Data, Big Data 7s, Big Data Analytics, dark data, data architecture, Data governance, Data Lake, data management, data science, Data Supply Framework, Data Warehouse, Data Warehousing, pig data, The Amazing Big Data Challenge, The Big Data Contrarians

≈ Leave a comment

Tags

Big Data, business strategy, Consider this, data, Data Warehouse, Information Technology, Martyn Jones, Martyn Richard Jones

“Half the time she did things not simply, not for themselves; but to make people think this or that; perfect idiocy she knew for no one was ever for a second taken in.”  Virginia Woolf, Mrs. Dalloway

It’s all very well for the blithering Big Data bullshitter savants to now claim, after a massive exercise in u-turning, that Big Data isn’t after all about data volumes, velocities and varieties, but about some minor variation on the theme of data architecture, management and processing.

But, look at the mess! Continue reading →

Too much information

16 Wednesday Mar 2016

Posted by Martyn Jones in 4th generation Data Warehousing, All Data, Ask Martyn, Big Data, Big Data 7s, Big Data Analytics, business strategy, dark data, Data governance, Data Lake, data management, data science, Data Supply Framework, Data Warehouse, Data Warehousing, Good Strat, Good Strategy, goodstrat, IT strategy, Marty does, Martyn does, Martyn Jones, Martyn Richard Jones, pig data, Strategy, The Amazing Big Data Challenge, The Big Data Contrarians

≈ Leave a comment

Tags

Big Data, Business Enablement, business intelligence, Business Management, Data Warehouse, Good Strat, Information Technology, Martyn Jones, Martyn Richard Jones, Organisational Autism, Strategy

Martyn Richard Jones

I have questions about data.

Most of us who have more than a cursory knowledge of the English language have heard of the phrase ‘too much information’. We know what it means, even if we don’t always know when to apply it.

For those who don’t know, or are unsure, the Urban Dictionary describes ‘too much information’ as “An expression of exasperation and disgust when a person is divulging personal details of his sex life, toilet habits, or anything the listener finds disgusting, uninteresting, and unwelcome.”[1]

Sum, sum. Just because we know it, doesn’t mean we should share it or even try and remember it, never mind go about analysing the hell out of it.

This is where Big Data comes in. Continue reading →

Big Data 7s: Talking Points #1

09 Friday Jan 2015

Posted by Martyn Jones in Big Data, Big Data 7s, Consider this, Data Warehouse

≈ Leave a comment

Tags

Big Data, business intelligence, data analytics, Data Warehouse

JPR-Williams_181887k

To begin at the beginning

This is the first in a series of collections of talking points on the processing of very large data sets by non-relational or pseudo-relational means, speculative data analytics with these large data sets which is typically non-operational data and social media data obtained from internet sources, and how usable outcomes, if any are derived, can be integrated into strategic, tactical and operational decision support.

Currently this area is parked under the misleadingly named ‘Big Data’ umbrella, but in the near future I predict that this niche will be merged into the more recognisable and business oriented areas of data warehousing, data architecture and business intelligence, and rebadged to avoid even further confusion.

Each number of this series will be addressing 7 talking points.

Here are the first seven talking points that deal with aspects of primal mass data processing, speculative analytics and outcome and result persistence and association.

Keep it simple

The leading and continuous mantra for all ‘Big Data’ initiatives should be simplicity.

Simplicity means identifying a well -bounded speculative opportunity and then focussing on it, whilst not allowing for scope creep until the work is done and a following iteration is defined.

Simplicity means taking the data that is needed, along with the useless baggage data that it is unfortunately bundled with, and then reducing the data to the essentials at the earliest possible moment.

Simplicity means trying to move the data reduction problem up stream, preferably to the point where it is actually generated and stored.

Simplicity means not flannelling business people about the supposed benefits of ‘Big Data’. It means about avoiding patronising language akin to “Just do Big Data, because everyone will have to be doing it, and don’t worry your pretty little head about what it’s actually doing under the bonnet”. It means being frank, open and earnest about ‘Big Data’.

Hold this thought: You cannot bullshit simplicity.

Appropriate is good

The great economist John Kenneth Galbraith once observed that “The real accomplishment of modern science and technology consists in taking ordinary men, informing them narrowly and deeply and then, through appropriate organization, arranging to have their knowledge combined with that of other specialized but equally ordinary men. This dispenses with the need for genius. The resulting performance, though less inspiring, is far more predictable.”

Appropriateness is one of the more important aspects of supplying data for strategic, tactical and operational decision support, and it is data that must by its very nature be appropriate.

Appropriateness addresses the need for the right data.

Hold this thought: Appropriateness is good

Adequate is sufficient

Another important aspect of Adequacy means that there is enough data supplied to adequately meet the requirements for that data. Adequacy addresses the need for the right volume of the right data and at the right levels of abstraction.

I know that people in IT find it tempting to second guess requirements and to pile up unasked for feature additions like they were going out of fashion, but in the lean and iterative age of agile we can no longer afford to be so reckless in how we manage requirements, projects and resources, especially those assigned to ‘Big Data’ projects.

Just hold this thought: Adequate really is enough

Timeliness kills the competition

Another important aspect of this Big Data field is found in the timely provision of data and the fast delivery of usable outcomes.  But this not only requires ‘Big Data’ but also big data management smarts.

Timeliness addresses the need to get appropriate and adequate data to decision makers on time and every time, in order to maximise the possibilities for its use and therefore to increase the chances of it having some business value.

Hold this thought: Speed kills the competition.

Integration makes sense

If after running speculative analysis (diagnostic or predictive, etc.) and you are lucky enough to actually end up with something tangible and useful, you may also want to consider linking this or integrating the outcomes into mainstream and quality assured strategic and tactical decision support and analysis data.

This is where the Data Warehouse concept of Bill Inmon comes into its own. Because Enterprise Data Warehousing (and especially DW 3.0) provides a conceptual data architecture and data management protocols to support the adequate, appropriate and timely scaling of data set sizes from gigabytes to terabytes and then to petabytes – and beyond, if that is really what is needed.

Hold this thought: Integrate without losing essence

Big Data Science name change

There has been so much misleading, unreliable and unrepresentative puff built up around Big Data that it seems like an appropriate time to give it a ‘legal, decent and honest’ makeover, and to also change its name to something more appropriate such as Janus Data Analytics (JDA for short) or New Wave Punk Data.

I believe that Janus Data Analytics may be a good name for this niche technology field because it accurately reflects what it is and at the same time it is intrinsically linked to beginnings and transitions, to gates, doors, doorways, passages and endings. Janus Data Analytics looks into the future and into the past, and presides over the beginning and ending of conflict, war and peace.

There is also a certain attraction in the term New Wave Punk Data. It sends a strong and uncompromising signal to business. It deftly and simply describes the two key aspects of what is being currently touted as ‘Big Data’. New Wave Punk Data reflects the rapid, sharp edged and primal slicing, dicing and reduction of very large data sets, together with short term speculation, stripped-down analytics, with often opinionated and alternative drivers. It embraces a DIY ethic; many businesses that lead the movement (Yahoo, Google, Facebook, etc.) started with self-developed ‘Big Data’ tools (often initially as simple variations on the Unix power-chord themes of parallel grep, awk and cat) and shared them through open source channels.

The third option is to simply place the data aspect of ‘Big Data’ under the data architecture and data management umbrella as a facet of Data Warehousing and to place the ‘data science’ aspect of ‘Big Data’ under the statistics and data analytics umbrella, with a close association with the sub-class known as business intelligence. The true data mining and machine learning aspects of ‘Big Data’ can sensibly continue under the umbrella of Artificial Intelligence.

Hold this thought: A rose by any other name

Keep it legal, decent and honest

Potentially there are methods, technologies and techniques under the ‘Big Data’ big-top that could be used to accrue real business value; however, those benefits are being put at risk by the quality and quantity of puff in the environment, which was alluded to in the previous talking point.

The point is this. Banging on about the same nebulous futures of ‘Big Data’ rather than being specific, clear and verifiable about what is really going on is, to state it simply, is going to ‘queer the pitch’ for everyone; the good, the bad and the ugly… but especially the good.

Therefore I would suggest that we all take an additional New Year’s resolution on ‘Big Data’, and in future only refer to the application and benefits of ‘Big Data’ and ‘Big Data’ analytics in terms that could only be construed as legal, decent and honest.

Hold this thought: “If you are not a better person tomorrow than you are today, what need have you for a tomorrow?” – Rebbe Nachman of Breslov

That’s all folks

So, that is all from me in the first of what I hope will be many issues in the series Big Data 7s.

I would like to leave you with this fabulous quote from James Carville… just because.

“Sometimes the right thing gets done for the wrong reason and sometimes, unfortunately, the wrong thing gets done for the right reason”.

As always, many thanks for reading.


File under: Good Strat, Good Strategy, Martyn Richard Jones, Martyn Jones, Cambriano Energy, Iniciativa Consulting, Iniciativa para Data Warehouse, Tiki Taka Pro

Big Data is Dead!

20 Saturday Dec 2014

Posted by Martyn Jones in Big Data, Data governance, Data Warehousing

≈ 6 Comments

Tags

Analytics, Big Data, Data Warehouse

BDID6

Alas, poor Yorick! I knew him, Horatio; a fellow of infinite jest, of most excellent fancy; he hath borne me on his back a thousand times; and now, how abhorred in my imagination it is!

From the play Hamlet by William Shakespeare

Big Data is dead! Long live Information Management. Continue reading →

Data Warehousing and Sources of Truth: Rarely Pure, Never Simple

19 Friday Dec 2014

Posted by Martyn Jones in Data Warehouse, Data Warehousing, EDW

≈ Leave a comment

Tags

Data Warehouse, single source of truth

1.       To begin at the beginning

“A thing is not necessarily true because a man dies for it.”

Oscar Wilde

For well over two decades one of the most talked about benefits of Enterprise Data Warehousing (EDW) has been that it gives us a single source of business truth. Continue reading →

Consider this: Did Big Data Kill The Statistician?

03 Wednesday Dec 2014

Posted by Martyn Jones in consider, Consider this, data science, statistics

≈ 20 Comments

Tags

Big Data, BS, Consider this, data analysts, data science, Data Warehouse, enterprise data warehousing, statisticians, statistics

OLYMPUS DIGITAL CAMERA

Blue sky data

Hold this thought: ‘There are big lies, damn big lies and big data science’.

Statistics is a science. Some argue that it is the oldest of sciences. It can be traced back in history to the days of Augustus Caesar, and before.

In 1998, Lynn Billard, in a paper that laid out the role of the Statistician and Statistics, wrote that “no science began until man mastered the concepts and arts of counting, measuring, and weighting”.[1]

Continue reading →

Consider this: Data Warehousing Without Tears

30 Sunday Nov 2014

Posted by Martyn Jones in Consider this, Data Warehouse, Data Warehousing

≈ Leave a comment

Tags

Data Warehouse, enterprise data warehousing, success factors

 Old advice is still good advice, if it is truly good advice.

It’s an older piece (from the nineties), but a lot of it is still relevant and pertinent.

So, here is a brief run-down on how to avoid crashing and burning Data Warehousing.

Understand that a Data Warehouse should only contain subject oriented, integrated, non-volatile and time-variant information to support strategic and tactical requirements of management – Keeping the purpose of the Data Warehouse highly focused will eliminate the dilution of a Data Warehouse solutions effectiveness. If what Bill Inmon said in this respect almost invariably results in successful DW projects – and that’s not speculation but proven fact – then I don’t see any rational reason at the moment to change our views on this.

Ensure High-level Business Sponsorship – A very old commentary by the Hurwitz group pointed to a Price Waterhouse Coopers survey that said that 67% of warehouses fail, and related successes to the fact that “successful warehouses received sponsorship from key business executives. Therefore, with the need to focus on answering business questions, data warehouses should be designed in a way that the information they contain and the structure that is used should be intuitive for business users to use.

Understand and Involve The Business User. Always – The Business End-Users of the Data Warehouse should form an integral part of the Data Warehouse project team – either directly, or in the case of a large user community, through adequate, appropriate and timely end-user representation. End-User participation in a project does not imply that everyone else can take a back seat. Every assistance possible must be given to ensure that the End-Users understand what is possible, how much it costs and how long it takes. Every relevant piece of data warehouse project data, information and knowledge must be made available to the End-User and when necessary explained to the End-User in terms they can understand. Don’t expect users to have all the answers or to be able to provide you with answers in precisely the form that you may be expecting those answers. Be understanding, be flexible, and also don’t forget that business is dynamic and in a state of almost constant change. Therefore, don’t just hypothesize about users changing their minds, one must expect it to happen. Anticipate change and prepare for it, embrace change and make it work for you. Let’s not ever forget that the building of a Data Warehouse is for the benefit of the whole business and a partnership in which everyone has a major stake.

Start with a Technology Pilot – One of the best ways to ensure the initial success of an Enterprise Wide Data Warehouse is to select an initial project that is:

  • Small enough to be achievable
  • Large enough to be significant
  • High business profile if successful

Don’t Make the DW an IT Project – I recommend that a Data Warehouse is first and foremost a Business Project that just happens to need information technology products and services. Don’t just hand-over all the responsibility for your Enterprise Data Warehouse project to the IT function – Make sure that the business is the DW owner and that End-Users drive the requirements specification.

Deliver Information Promptly – You should aim at delivering information to the End-User within a 3 to 4 month time-scale for the first iteration, and below a 3 month time-scale for subsequent iterations. There is nothing so successful in setting realistic user expectations and then delivering on them promptly and accurately.

Truly Empower The Business User – The data warehouse is a way to provide adequate, appropriate and timely information to the business so that users will be able to create all their own reports and information analysis. The data warehouse should be used to throw out many of the dependencies of Business Users on IT. The data warehouse avoids the need and cost of providing them with support, that inadequate and dependency building support that they themselves should not need if they are adequately trained, encouraged and empowered.

Use the Iterative and Agile Approach to the Max – Most companies are faced with enormous amounts of data, in many formats that could potentially be located in a data warehouse. But operational systems, for example, have large amounts of transaction-level data that may or may not be required for analysis. Trying to locate all this corporate data at once is generally not feasible – for logistical and cost reasons alone. If, however, a company can build its data warehouse by moving portions of the data incrementally, as needed to solve a specific business problem, the process becomes safer, more manageable, and less costly, providing a faster return on investment. For example, a telecommunication company can start by consolidating all its customer information in a data warehouse in order to understand how to maintain better relationships with existing customers.

The use of the iterative development approach is the most effective way to balance timely delivery with the complexities of the telecommunications environment – the iterative approach is an integral feature of the iniciativa/ISF methodology. There are five major drivers that lead us to an iterative development approach:

The value of information will change.

The complete value chain of information must be understood and delivered, this is known as a dynamic characteristic.

The business processes will continue to change and be refined

Scalable technology decisions will need to change and be refined.

A flexible organization must be supported.

Iterative development speeds the delivery of benefits to users. An initial iteration can deliver limited functionality to a select group of users. Later iterations can be built upon the work of the first, decreasing the amount of effort. The iterations can be carefully planned to deliver the complete value chain of information delivery using your own business priorities as drivers.

Drive a Corporation Data Source Audit – It may be a good idea to run a parallel sub-project to identify and catalogue all possible data sources throughout the enterprise. It may be a good idea to include as much meta-data type information as possible: data source, platform, database, predicted quality and reliability. In the audit process do not forget to take into account systems either in the planning, analysis or development stage. However, don’t let this task be an excuse for letting “analysis paralysis” damage your Data Warehouse project.

Give the users what they want but don’t create unrealizable expectations – the key to business success has been described as that of knowing what the users want and then giving them what they want. However, don’t promise focused, adequate, appropriate and timely information if you can’t deliver on that promise.

Ensure accuracy and understand Data Quality issues – Ensure that the information you supply to users is accurate enough to be truly useful and that your data quality standards are realistic and cost-effective.

Scalability and Architecture – If your data warehouse is successful it will grow – in terms of data volumes, number of users and processing demand. Ensure that the technological architecture chosen for your solution is capable of adapting to the evolving needs of the business and the ability to build an adaptive framework to evolve with the business requirements

Take Advantage of Others Knowledge, Experience and Technologies – But Don’t Be Taken Advantage of – Data Warehousing is a process that requires significant amounts of know-how and experience to get it right. It pays to work with people who have done Data Warehousing in Telecoms successfully before – even if there is generally an aversion to using 3rd party consulting services pick and match your needs with what is available. Don’t limit your ability to deliver the right solution on time by short sightedness or a not-invented-here syndrome. On the other hand, beware of companies that offer to build – for example – a customized generic Telecoms DW data model with three senior consultants in three months – for more information on Data Modeling in a Banking, Government or Telecoms contact you should contact Cambriano (martyn.jones@cambriano.es), or any other reputable consulting organization.

Understand, Plan For and Manage the Impact of the Data Warehouse of the IT Infrastructure – It is important to understand the impact of the Data Warehouse on the IT infrastructure and to plan accordingly. Moving large volumes of data from Operational Systems to the Data Warehouse – Extraction, Transformation and Transportation of data – and end-user usage of the Data Warehouse signifies additional and significant impact on the IT infrastructure, i.e.:

  • Additional processing loads on the source data OLTP systems
  • Additional traffic on the corporate network – do you upgrade the network for increased band-width and network speed?
  • Additional administration and support workload for IT Infrastructure staff
  • Additional users of the DW occupying network space
  • Additional availability demands on OLTP systems – e.g. Data Warehousing ETT demands may reduce ability to plan for OLTP batch job re-runs

Therefore, understanding and planning for the Data Warehouse and its impact on the IT Infrastructure in a critical success factor.

Transform and Structure – Take full advantage of the most appropriate ETT (now called ETL or integration) tools and DW data modeling techniques to provide integrated data and information in a form that business users understand and that is easy for them to use. Don’t be put off by the apparent simplicity of the Extract/Transform/Transport process for the first iteration, although the idea of hand-crafting ETT processes using 3GL code is aesthetically pleasing the process does get more complex to develop and maintain after iteration one. Bottom line: DIY ETT sounds simple, using an ETT tool sounds more complex, and the simplicity of DIY is as false as the simplicity of DW ETT process maintenance using an ETT tool is true.

End-User Tools that best match existing and known paradigms work well in the short term – End-users who are used to working with products such as MS/Excel will also find products such as BusinessObjects fairly easy to come to terms with. Some access to the information in the Telecoms Data Warehouse will almost invariably have to be provided via a canned interface.

Market the success of the Data Warehouse – Encourage Business Users to discuss why the Data Warehouse has improved their ability to fulfil their missions. Publish newsletters containing surveys, success stories and End-User guides to getting the best from the information in the DW. Start a competition to find a good name for your Data Warehouse and Data Warehouse project A short memorable name and a simple and effective logo will create a greater sense of identity and purpose.

Getting Users to Justify the Data Warehouse Success leads to more success – a product’s best salesperson is the customer (End-User) not the provider (iniciativa in Spain and South and Central America, and Cambriano Energy for USA and Europe or even your own IT organization).

Encourage users to justify why they need the Data Warehouse – keep business users and business stakeholders satisfied and encourage this DW justification from these users and stakeholders on an on-going basis.

Trust and Confidence Ensure that End-Users are satisfied with the quality of the data warehouse service and that they can trust the quality of the DW data.

Single Point Of Contact Provide your End-Users with a single point of contact for all routine queries – Allow them simple and effective means to escalate issues if they do not get satisfaction. Make sure they understand the process fully. Make sure your Single Point of Contact has the empowerment to be as flexible, dynamic and rapid in dealing with business customers.

Partner with an experienced and knowledgeable consulting team – one who will fully understand the wide range of aspects and components required to successfully deliver the advantages of Corporate Data Warehousing. A true partner that well understands the needs and the dynamics of your marketplace. Or better still, give me a call or drop me a line.

Many thanks for reading. I hope it gave you some useful or though provoking take-aways.


File under: Good Strat, Good Strategy, Martyn Richard Jones, Martyn Jones, Cambriano Energy, Iniciativa Consulting, Iniciativa para Data Warehouse, Tiki Taka Pro

Consider this: Ten thoughts on Data Warehousing

30 Sunday Nov 2014

Posted by Martyn Jones in Ask Martyn, Consider this, Data Warehouse, Data Warehousing

≈ Leave a comment

Tags

Consider this, Data Warehouse

More than 80% of advertising is ignored. More than 50% of Data Warehouse projects fail in one way or another. The information explosion has been accompanied by a massive increase in the ranks of the willfully stupid.

  1. The term is “Data Warehousing”. Data Warehousing does all the heavy lifting which Business Intelligence selection, analysis and visual presentation tools can then exploit.
  2. Data Warehousing is strategic, tactical and exploratory, all other information supply is either operational or superfluous, and should be provided by your operational systems and 3rd party providers, such as the big ERP vendors (SAP, Oracle, Microsoft, and etcetera).
  3. Data Warehousing is fundamentally about business process and should be solely driven by business imperatives. Without business imperatives there is no reason for the existence of a Data Warehouse.
  4. To understand Data Warehousing you must be also capable of understanding business process.
  5. An adequate understanding of business process is not typically taught in classes on ETL, UNIX, RDBMS or Middleware, etcetera.
  6. The four key defining features of Data Warehousing were first documented by Bill Inmon[1], and should be the first criteria to be tested in each and every iteration of a Data Warehouse.
  7. Ralph Kimball is the most visible and successful advocate of the very useful ‘star schema’ dimensional model.
  8. Data Warehousing is about improvement through business driven innovation and creative use.[2] Data Warehousing isn’t about “expanding the menu”.
  9. A data warehouse business process must be continually subjected to testing, including risk and requirements based testing.
  10. Data Warehousing is part of an organization’s intellectual capital, and must be handled as the asset that it is. For example, although many businesses do this, the outsourcing and especially offshoring of your intellectual capital processes, initiatives and projects is always abject folly.

So, thanks for reading and until next time. Ciao!

[1] Subject oriented; integrated; time variant; and, non-volatile.

[2] “Innovation’ isn’t what innovators do….it’s what customers and clients adopt.” – Michael Schrage


File under: Good Strat, Good Strategy, Martyn Richard Jones, Martyn Jones, Cambriano Energy, Iniciativa Consulting, Iniciativa para Data Warehouse, Tiki Taka Pro

Responsible Use of Corporate Data

03 Monday Nov 2014

Posted by Martyn Jones in Ask Martyn, Best principles, Data governance

≈ Leave a comment

Tags

Big Data, Business, business intelligence, data governance, data management, Data protection, Data Warehouse, privacy, Strategy

IMGThere was a time, when absolute discretion was an important maxim in the relationship between a liberal professional (doctor, banker, solicitor, architect etc.) and their clients, but times have changed, and are continuing to transform at an ever increasing pace. Continue reading →

Strategic Fit – Function Drives Form

14 Tuesday Oct 2014

Posted by Martyn Jones in Architecture, awareness, Management, Strategy

≈ Leave a comment

Tags

accountability, awareness, business analysis, constraints, Data Warehouse, modelling, opportunities, organisational awareness, Strategy

Strategic fit express the degree to which an organization is matching its resources and capabilities with the opportunities in the external environment.

The matching takes place through the practice of pre-strategy analysis.

That stated, it is very easy to fall into the trap of simplifying the high level concepts and overstating the intricacies and interdependence of strategic-fit factors. Continue reading →

← Older posts
Follow GOOD STRATEGY on WordPress.com

Top posts

  • Heaven help us! Have you seen the latest Virtual Data Warehouse bullshit?
  • Data Warehousing and Sources of Truth: Rarely Pure, Never Simple
  • The World's Best Data Quotes... Including Big Data quotes
  • Become an Instant Big Data Rock Star with 10 Insider Tips from the Top
  • Agile at Scale is bullshit by design
  • Bullshit at the Data Lakehouse
  • Head Over Heels - The many colours, hues and tones of poems, lyrics and words

Enter your email address to follow this blog and receive notifications of new posts by email.

Join 2,439 other subscribers

Names in the cloud

4th generation Data Warehousing All Data Ask Martyn Big Data Big Data 7s Big Data Analytics Business Intelligence business strategy Consider this dark data data architecture Data governance Data Lake data management data science Data Supply Framework Data Warehouse Data Warehousing Good Strat goodstrat Good Strategy IT strategy Martyn does Martyn Jones Martyn Richard Jones pig data Politics Strategy The Amazing Big Data Challenge The Big Data Contrarians

The Good Strat Archives

  • March 2023
  • January 2022
  • December 2021
  • November 2021
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • July 2019
  • June 2019
  • May 2019
  • December 2018
  • January 2018
  • December 2017
  • October 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • September 2016
  • August 2016
  • May 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014

The Stats

  • 99,717 hits

Recent posts

  • You don’t need a data warehouse to do data warehousing March 22, 2023
  • Data Warehousing means having thousands of ETL jobs March 21, 2023
  • The data warehouse is the repository for the post-transactional data March 20, 2023
  • Does your way of providing data have business value? March 19, 2023
  • Data warehousing stands in the way of progress March 18, 2023
  • Data Trailblazers: 2022 Vision January 2, 2022
  • Tea with The Data Contrarian: Afilonius Rex December 10, 2021
  • Reality Check: Data Mesh and Data Warehousing   December 5, 2021
  • Myth-busting: Data Mesh and Data Warehousing – Revisited November 25, 2021
  • Heaven help us! Have you seen the latest Virtual Data Warehouse bullshit? June 26, 2020

Hours & Info

Martyn Richard Jones
Madrid, Spain
+33 767 120 160
10:00 - 17:00
Follow GOOD STRATEGY on WordPress.com

Follow me on Twitter

My Tweets

Top Good Strat Posts & Pages

  • The Good Strategy Company
  • Heaven help us! Have you seen the latest Virtual Data Warehouse bullshit?
  • About
  • Data Warehousing and Sources of Truth: Rarely Pure, Never Simple
  • The World's Best Data Quotes... Including Big Data quotes
  • Become an Instant Big Data Rock Star with 10 Insider Tips from the Top
  • Agile at Scale is bullshit by design
  • Bullshit at the Data Lakehouse
  • Head Over Heels - The many colours, hues and tones of poems, lyrics and words

Good strat tag cloud

accountability advertising All Data Analytics aspiring tendencies in IM awareness Banking Behavioural Economics BI Big Data Bill Inmon Brexit BS Business business analysis Business Enablement business intelligence Business Management business strategy Challenges Commercial IT Consider this corporate assets Corporate IT Creativity data data analytics data architecture data integration data management Data Marts data science Data Warehouse Demagogism Dogma DW 3.0 Economics enterprise data warehousing EU Financial Goal Setting goodstart good start Good Strat goodstrat Good Strategy hadoop Information and Technology information management Information Technology IT business IT Strategy knowledge management leadership marketforces Marketing Martyn Jones Martyn Richard Jones MDM Offshoring operationalwareness Organisational Autism organisational awareness Outsourcing Pimps Politics project management Requirements management Risk Risk Management statistics Strategy trading traditional assets UK

Categories

  • 4th generation Data Warehousing
  • accountability
  • advertising
  • agile
  • agile way of working
  • agile@scale
  • AI
  • All Data
  • Analytics
  • anthropology
  • Architecture
  • Artificial Intelligence
  • Ask Martyn
  • Assets
  • awareness
  • bad strategy
  • Banking
  • behaviour
  • Best principles
  • Big Data
  • Big Data 7s
  • Big Data Analytics
  • blockchain
  • Books with influence
  • Brexit
  • BS
  • business
  • Business Intelligence
  • business strategy
  • Cambriano
  • Cambridge Analytica
  • China
  • Climate Change
  • Cloud
  • code of conduct
  • Commercial Analytics
  • community
  • Condiser this
  • Conservative Party
  • consider
  • Consider this
  • Consultation
  • Creativity
  • dark data
  • data
  • data architecture
  • Data governance
  • data hub
  • Data Lake
  • data management
  • Data Mart
  • data mesh
  • data science
  • Data Supply Framework
  • Data Warehouse
  • Data Warehousing
  • deceit
  • deep learning
  • Democracy
  • digital transformation
  • Diplomacy
  • disinformation
  • Dogma
  • Duties
  • DW 3.0
  • ECM
  • Economics
  • EDW
  • England
  • enterprise content management
  • ethics
  • EU
  • Europe
  • European Union
  • Excellence
  • Excerpt
  • Executive
  • Extract
  • Federalism
  • Financial Industry
  • fraud
  • Freedoms
  • Globalisation
  • good start
  • Good Strat
  • Good Strategy
  • Good Strategy Radio
  • goodstart
  • goodstartegy
  • goodstrat
  • goostart
  • governance
  • hadoop
  • hdfs
  • HR
  • humour
  • India
  • influencers
  • informatio Supply Framework
  • information
  • Information Management
  • Information Supply Frameowrk
  • Information Supply Framework
  • Infotrends
  • Inmon
  • instruments
  • IoT
  • IT Circus
  • IT fraud
  • IT strategy
  • IT World
  • iterations
  • java
  • Knowledge
  • knowledge management
  • Labour Party
  • leadership
  • Leadership 7s
  • life
  • listening
  • literature
  • LSE
  • machine learning
  • Management
  • market forces
  • Marketing
  • Marty does
  • Martyn does
  • Martyn Jones
  • Martyn Richard Jones
  • media
  • Memory lane
  • Methodology
  • nationalism
  • nine competitive forces
  • no limits
  • Northern Ireland
  • obituary
  • Obligations
  • offshore
  • Offshoring
  • operational
  • Outsourcing
  • Oxford
  • pain
  • Parliament
  • Peeves
  • Personal Integrity Key
  • Philosophy
  • pig data
  • PIK
  • PIR
  • Plaid Cymru
  • Planning
  • poem
  • poems
  • Poetry
  • Polemic
  • political science
  • Politics
  • pomo
  • postmodern
  • POTUS
  • Process
  • Professional Networking
  • professionalism
  • project management
  • Project to Excel
  • prose
  • public
  • Public Integrity Record
  • Quiz
  • Rant
  • Referendum
  • Remain
  • RIghts
  • Risk
  • Rivalry
  • Russia
  • Ruth Davidson
  • Sales
  • satire
  • Scotland
  • Scottish National Party
  • scrum
  • sentiment analysis
  • SMILES
  • Snippet
  • SNP
  • Social
  • Social Media
  • Sociology
  • spoof
  • statistics
  • Stories
  • Strategy
  • structured intellectual capital
  • supply chain management
  • tactics
  • Tax avoidance
  • Tax evasion
  • TEAM
  • technology
  • The Amazing Big Data Challenge
  • The Big Data Contrarians
  • The Greens
  • The Guardian
  • The hidden wealth of nations
  • Trade
  • UK
  • Uncategorized
  • United Kingdom
  • USA
  • Value
  • Wales
  • wisdom

Blog at WordPress.com.

  • Follow Following
    • GOOD STRATEGY
    • Join 131 other followers
    • Already have a WordPress.com account? Log in now.
    • GOOD STRATEGY
    • Customize
    • Follow Following
    • Sign up
    • Log in
    • Report this content
    • View site in Reader
    • Manage subscriptions
    • Collapse this bar
 

Loading Comments...
 

    Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
    To find out more, including how to control cookies, see here: Cookie Policy