It is important to understand the difference between the LINQ methodology and other diagramming methodologies you may use in your business.
So how do you Think Like LINQ?
The "other" ways of viewing the IT Enterprise involve using specialist tools. Each tool focuses on a specific aspect of IT, for example Enterprise Architect for system architecture, or Business Process Modelling for processes and actions.
The resulting content from these tools tend only to be understood by technical experts and there is no easy way to translate the language that they use between these tools and methodologies. If you aren't the expert in all of them, it can be hard to achieve a whole view of the IT infrastructure. Taking that view to the decision maker becomes even harder. How do you translate between all of these tools into language that a Senior Leader can understand so that they are able to make the right decision about the next steps to take. There is a good example of this on our blog here.
LINQ looks at IT from the perspective of how information flows or is transmitted through the IT infrastructure. We call these Information Supply Chains (ISCs). ISCs support Knowledge Manufacturing - another term you will hear often through your LINQ journey.
LINQ doesn't compete with these other tools; it complements them. LINQ fits in that gap between the expert tools you already use and the Decision Maker who needs to understand what they should spend their budget on, and why.
You do however, need to Think Like LINQ. This is that guide.
LINQ is a language. There are only 4 nodes that we consider and they are linked together like this:
These nodes are used to describe reality. This is a very important concept - we are not describing what we would like reality to be - we are describing what reality really is, on the ground in the organisation, warts and all!
What you'd like reality to be is a possible future state, not current state. Your first use of LINQ is all about capturing your Current State.
Now let's put this all together.
Our YouTube Channelyou can see a number of short videos which take you through the Quick LINQ process and then also expand into some of the Information Supply Chain capture detail.
In the meantime, please use this forum to engage with us. Ask questions, pose scenarios, etc. and we will happily help you to Think Like LINQ.
Neil Calvert
It is important to understand the difference between the LINQ methodology and other diagramming methodologies you may use in your business.
So how do you Think Like LINQ?
The "other" ways of viewing the IT Enterprise involve using specialist tools. Each tool focuses on a specific aspect of IT, for example Enterprise Architect for system architecture, or Business Process Modelling for processes and actions.
The resulting content from these tools tend only to be understood by technical experts and there is no easy way to translate the language that they use between these tools and methodologies. If you aren't the expert in all of them, it can be hard to achieve a whole view of the IT infrastructure. Taking that view to the decision maker becomes even harder. How do you translate between all of these tools into language that a Senior Leader can understand so that they are able to make the right decision about the next steps to take. There is a good example of this on our blog here.
LINQ looks at IT from the perspective of how information flows or is transmitted through the IT infrastructure. We call these Information Supply Chains (ISCs). ISCs support Knowledge Manufacturing - another term you will hear often through your LINQ journey.
LINQ doesn't compete with these other tools; it complements them. LINQ fits in that gap between the expert tools you already use and the Decision Maker who needs to understand what they should spend their budget on, and why.
You do however, need to Think Like LINQ. This is that guide.
LINQ is a language. There are only 4 nodes that we consider and they are linked together like this:
These nodes are used to describe reality. This is a very important concept - we are not describing what we would like reality to be - we are describing what reality really is, on the ground in the organisation, warts and all!What you'd like reality to be is a possible future state, not current state. Your first use of LINQ is all about capturing your Current State.
Now let's put this all together.