<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://debianws.lexgopc.com/wiki143/index.php?action=history&amp;feed=atom&amp;title=Technology_alignment</id>
	<title>Technology alignment - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://debianws.lexgopc.com/wiki143/index.php?action=history&amp;feed=atom&amp;title=Technology_alignment"/>
	<link rel="alternate" type="text/html" href="http://debianws.lexgopc.com/wiki143/index.php?title=Technology_alignment&amp;action=history"/>
	<updated>2026-05-11T18:08:45Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.1</generator>
	<entry>
		<id>http://debianws.lexgopc.com/wiki143/index.php?title=Technology_alignment&amp;diff=1462775&amp;oldid=prev</id>
		<title>imported&gt;Bunnypranav: Add ref list, AWB cleanup</title>
		<link rel="alternate" type="text/html" href="http://debianws.lexgopc.com/wiki143/index.php?title=Technology_alignment&amp;diff=1462775&amp;oldid=prev"/>
		<updated>2024-10-26T17:02:26Z</updated>

		<summary type="html">&lt;p&gt;Add ref list, AWB cleanup&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{multiple issues|&lt;br /&gt;
{{more citations needed|date=October 2024}}&lt;br /&gt;
{{essay|date=October 2024}}&lt;br /&gt;
{{original research|date=October 2024}}&lt;br /&gt;
}}&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Business and technology alignment&amp;#039;&amp;#039;&amp;#039;, or just &amp;#039;&amp;#039;&amp;#039;technology alignment&amp;#039;&amp;#039;&amp;#039;, corrects terminology and assumptions used in business to better match those of technology and standards anticipated in the [[technology strategy]] and [[technology roadmap]]s.&amp;lt;ref&amp;gt;{{Cite web |title=7 Steps to Business and IT alignment |url=https://cioindex.com/reference/7-steps-to-business-and-it-alignment/}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Changes terminology ==&lt;br /&gt;
{{unreferenced section|date=October 2024}}&lt;br /&gt;
When technology is changing very rapidly in an industry, the aligning of business terms to the distinctions that the technology requires tends to dominate any [[enterprise taxonomy]] development effort. In such circumstances, [[consultant]]s or specific technology training is usually required, as the organization lacks the internal skills or experience with the technologies that it expects to be using soon.&lt;br /&gt;
&lt;br /&gt;
== Example: government ==&lt;br /&gt;
{{unreferenced section|date=October 2024}}&lt;br /&gt;
In [[government]], for example, citizen use of the [[Internet]] and the increased availability of [[remote work]] has presented special challenges and opportunities, typically called &amp;quot;[[e-government]]&amp;quot;. At the same time, internal operational efficiencies have become more of a priority due to rising competition between jurisdictions. Often the first step is to limit the number of different departments or agencies involved. By &amp;quot;consolidating the technology operations of 91 state agencies into the [[Virginia Information Technology Agency]], the State of Virginia estimates an eventual savings of nearly $100 million a year.&amp;quot; - [https://web.archive.org/web/20060923031105/http://cpr.ca.gov/report/cprrpt/issrec/stops/it/so01.htm#6b]&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Similarly, the [[U.S. National Performance Review]] recommended a data processing consolidation and modernization initiative citing industry experience suggesting operational savings of between 30% and 50%.&amp;quot; - [https://web.archive.org/web/20060923031105/http://cpr.ca.gov/report/cprrpt/issrec/stops/it/so01.htm#7b]&lt;br /&gt;
&lt;br /&gt;
While &amp;quot;California is the cradle of the information technology industry&amp;quot; its own state government claims that &amp;quot;collaborative exploration and exploitation of emerging technologies is extremely rare within state government&amp;quot;, accordingly it seeks to &amp;quot;[[customer relationship management|improve customer relationships]] through [[online service]]s.&amp;quot; However such efforts tend to rely very much on driving personalities and [[leadership]]. After one resignation, the state &amp;quot;lost the vision and executive sponsorship that contributed to its success and the national recognition of California&amp;#039;s emerging eGovernment activities.&amp;quot; This is a major problem in all technology alignment.&lt;br /&gt;
&lt;br /&gt;
In Canada, a similar nationwide effort called [[Service Canada]] has similar goals, and has run into similar problems: &amp;quot;The big complaints are that departments fight over their turf and are organized to serve the bureaucracy, not Canadians. They don’t [[data dictionary|share data]], [[enterprise taxonomy|information]], [[Information Infrastructure|common infrastructure]], [[information technology|technology]] or integrate their [[business process]]es. Senior bureaucrats are often accused of being out of touch with the needs of Canadians.&amp;quot; - [http://openpolitics.ca/Service+Canada] The government claims that it &amp;quot;is expected to save C$3 billion over five years by automating manual operations, consolidating [[call centre]]s and reducing overpayments in [[Canada Pension Plan]] and employment service.&amp;quot; It &amp;quot;will need to spend about C$500 million for technology, consolidate or move offices and retrain the thousands of workers whose jobs were eliminated by automation.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
When, as in California or Canada, new leadership and massive change to operations is required, technology alignment may simply excuse a massive [[business process reengineering]] and [[Layoff|downsizing]] exercise. This too is a common situation in technology alignment: using the fact of new technology as a pretext for other large changes.&lt;br /&gt;
&lt;br /&gt;
However, as with all such exercises, there are claims that better service will result, by (in Canada) &amp;quot;opening new offices and creating more front-line jobs in local communities&amp;quot; or (in California) &amp;quot;a 20% reduction in the workforce performing shared services&amp;quot; and of &amp;quot;nearly 9,000 state employees... about 3,600 are engaged in common core functions. An eventual 20% reduction in this workforce segment is possible through attrition when phased in over 5 years.&amp;quot; - [https://web.archive.org/web/20060923031105/http://cpr.ca.gov/report/cprrpt/issrec/stops/it/so01.htm#69b]&lt;br /&gt;
&lt;br /&gt;
These claims also are fairly typical: despite a longstanding admission among experts that there is a &amp;quot;[[productivity paradox]]&amp;quot;, the introduction of new information technology and more automated work processes are always assumed to be &amp;quot;more efficient&amp;quot; than what they replace. Accordingly, technology alignment is probably not a passing fad, but, seems to be driven by factors built into business and technology culture.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
== Sources ==&lt;br /&gt;
*[https://web.archive.org/web/20060923031105/http://cpr.ca.gov/report/cprrpt/issrec/stops/it/so01.htm the State of California performance review]&lt;br /&gt;
&lt;br /&gt;
[[Category:Technology strategy]]&lt;/div&gt;</summary>
		<author><name>imported&gt;Bunnypranav</name></author>
	</entry>
</feed>