82,883
edits
IT strategy: Difference between revisions
no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Ground up IT strategy | Ground up {{tag|IT strategy}} | ||
The [[innovation paradox]] | |||
==What is your ''hole''?== | |||
what do you want? In Management Consultant speak, what is your “key objective”? | |||
*The customer in the hardware store doesn't want a power drill. She wants ''a hole in the wall''. (Theodore Levitt) | |||
*The question is not "could we have a chatbot" but ''what is the problem we are trying to solve?''. | |||
==What is technology?== | ==What is technology?== | ||
It's not just about computers | It's not just about computers | ||
*The primarily technology we deal with is | *The primarily technology we deal with is [[legal technology]]. We need to simplify that before we can simplify the computer tech. - See: ''[[strategic over tactical]]'' | ||
*The first step to simplifying legal technology is to simplify the source code on which legal technology is compiled: Language | *The first step to simplifying legal technology is to simplify the source code on which legal technology is compiled: Language | ||
**Plain English isn't a fad or an optional extra. It's a fundamental design principle. It's easier and cheaper to ''code'' for plain English. | **Plain English isn't a fad or an optional extra. It's a fundamental design principle. It's easier and cheaper to ''code'' for plain English. | ||
| Line 11: | Line 15: | ||
*To buy new IT (Bottom line expense) | *To buy new IT (Bottom line expense) | ||
*To package/maintain/install IT (Technology resource) | *To package/maintain/install IT (Technology resource) | ||
*To configure new IT for | *To configure new IT for the firm (Technology resource) | ||
*To configure for use by legal (Legal/Technology resource) | *To configure for use by legal (Legal/Technology resource) | ||
*To train users (internal Legal/Technology resource) - do not underestimate the importance and difficult of this | *To train users (internal Legal/Technology resource) - do not underestimate the importance and difficult of this | ||
| Line 22: | Line 26: | ||
**technological: don’t understand/like new technology; significant change fatigue | **technological: don’t understand/like new technology; significant change fatigue | ||
**Technical: Our skill is creating and articulating bespoke solutions, not commoditising standard ones. | **Technical: Our skill is creating and articulating bespoke solutions, not commoditising standard ones. | ||
**Lawyers don’t write well. Legal drafting is convoluted, over- | **Lawyers don’t write well. Legal drafting is convoluted, over-particularized, prone to formalistic negotiation ([[for the avoidance of doubt]]...) and error (the inevitably missing “[[not]]”) | ||
*User knowledge is imperfect | *User knowledge is imperfect | ||
**Individuals who don’t understand policies are incentivised to apply them literally (being institutionally short an option - see below) | **Individuals who don’t understand policies are incentivised to apply them literally (being institutionally short an option - see below) | ||
**Institutional Knowledge: Generally is good | **Institutional Knowledge: Generally is good but we leak institutional knowledge and it is not tracked and captured. | ||
*Institutional knowledge is poor | *Institutional knowledge is poor | ||
**We don’t track our decisions - no MI kept on litigation close shaves; which issues come up and which don’t. | **We don’t track our decisions - no MI kept on litigation close shaves; which issues come up and which don’t. | ||
| Line 46: | Line 50: | ||
**Workshare | **Workshare | ||
*Opportunities to enhance/improve existing tools | *Opportunities to enhance/improve existing tools | ||
*Easy implementation to enhance interaction and connectivity | *Easy implementation to enhance interaction and connectivity | ||
**“Business Data Catalogs” to interrogate external databases from within Sharepoint | **“Business Data Catalogs” to interrogate external databases from within Sharepoint | ||
**Application Interfaces (“API”s) | **Application Interfaces (“API”s) | ||
*Open source solutions - There is a lot of good, free software available (e.g. | *Open source solutions - There is a lot of good, free software available (e.g. Mediawiki) | ||
*You have to spend to save: Some technology is worth investing in. | *You have to spend to save: Some technology is worth investing in. | ||