Environments that encourage learning, sharing and discovery will prosper. Environments that don't will not achieve high performance. I snickered at this title when I first thought about it. How does one "create" a "data culture" exactly? Previously I discussed training, tracking and reporting successes, all...
Predictive analytics should not be part of your initial BI system deployment. When you have finished building the BI system workflows and data warehouse, you have established the foundations for predictive analytics. Predictive analytics uses machine learning and artificial intelligence (ML/AI) applied to historical data...
How do you measure the hard and soft benefits? Some improvements are easy to measure because you can point to a singular discovery that led to improvement. People love showing others how their discovery improved efficiency or illuminated a previously unknown issue. Record these success stories,...
Most people call these support groups centers of excellence. "Center of Enablement" has a more helping vibe. The idea behind a CoE is to help your entire team obtain more knowledge and skill in: Data tools you’ve selected Extraction Loading Transformation Storage (database) Design (architecture,...
Establishing a business intelligence system creates the conditions for reliable data and high-quality information: disciplined maintenance, a framework of tools and ongoing training, all of which foster confidence and motivation. The Center of Enablement (CoE) provides ongoing expertise and support to encourage a healthy data...
BI System maintenance is like a teenager's bedroom—you should anticipate some challenges to maintain organization and reliability. Without discipline, the health and efficacy of your system won't last. Establishing best practices for monitoring and maintaining the system's health, security and performance is an integral part...
Security is a bad word in some companies because the IT guys don't get rewarded for making data accessible. They do, however, get punished for data breaches. Those who have worked for a company that has experienced a data breach have an appreciation for how...
A system-wide data workflow for an analytical business information system is a high-level map of a BI System. Summarizing data movement from data sources through the ELT processes and, finally, the presentation layer. Figure 3.3.1 The Unified Data Workflow The figure highlights broad categories of sources, activities,...
It's impossible to graft a fixed number of data workflows onto every business, non-profit or government entity that is definitive. However, standard data workflows provide generalization and repeatable starting points. Typical Milestone Durations Guidelines for work durations, assuming you have a team dedicated to the project: Many SaaS...
Licensing SaaS (software-as-a-service) products can be complicated. Every vendor wants to encourage commitment. Commitment comes in long-term contracts of one or more years, with better prices associated with longer commitments. Clients ask InterWorks to help them make contract capacity and term commitment decisions. Once we have...
In the last post, I provided guidelines on security and preventing unauthorized access to your data. I warned you that an overly restrictive security model could encourage bad behavior. BI system security is like my wife's purse. I might want to look inside, but I wouldn't...
Security and data governance are often treated as the same thing. They aren't. Security is about preventing unauthorized access. Governance is making it easier for people to find the information they need. One is about prevention, and the other is about inclusion. IT staff are rarely...
If you skimp on training, you may burn every penny you save later in the project when it's inconvenient and more costly. Even your expert team members need training and time to become confident in their skills and knowledge of new tools and methods. Your core...
Most people in your company are not database experts. They are interested in something other than databases and ELT programs. They want information that supports their work needs. Human beings are visual creatures, and interactive dashboards are visual data expressions. Dashboards enable everyone to see, understand...
The plans, quotes and project deliverables your selected consulting partner helped you develop should include a proof-of-concept project recommendation based on your combined due diligence. The proof-of-concept (POC) sprint is a crucial subproject that tests your platform and software selections. The first dashboards your end users...
Data workflows are like hiking boots — good-fitting ones can take you anywhere. Ill-fitting ones spawn misery. As you document the existing workflows in discovery meetings, these details will influence your software selections — the tools for the data workflows. The amount and type of work...
An essential part of any business intelligence system plan is to collect information on the vital data workflows within your company. An ounce of discovery is worth a pound of remediation. -Adapted from Benjamin Franklin During discovery, identify the business processes that comprise operations and provide data outputs....
This section summarizes the skills and knowledge your deployment team must have. Your deployment team will set up the software, define the proof-of-concept (POC) deliverables and perform efficacy testing. They will work with your consulting partner and end users to ensure the project deliverables meet...
A strategy vision roadmap (SVR) is a document that details the purpose of the project, expected benefits, training plans, project timeframe, proof-of-concept testing and validation. The SVR summarizes the overall project plan while also time-phasing all significant sub-projects (sprints) necessary to complete all the deliverables....
In this post, I'll cover team composition, focusing on technical and operational staff that will form the core of your team. The need for more detailed information about your business drives the desire to deploy a BI system. Typical goals include achieving better reporting, more detailed...
Interworks GmbH
Ratinger Straße 9
40213 Düsseldorf
Germany
Geschäftsführer: Mel Stephenson
Kontaktaufnahme: markus@interworks.eu
Telefon: +49 (0)211 5408 5301
Amtsgericht Düsseldorf HRB 79752
UstldNr: DE 313 353 072