--- > Thinking about technology as "soft," as an aspect of an organization's staff, style and skills, may seem counterintuitive, but increasingly this is where it truly resides (and it's where you'll have the greatest leverage when driving technology-related change.) - [View Highlight](https://read.readwise.io/read/01h12gprkt067bsyvx6x8rsz2d) --- > I think part of the problem was the language I used to introduce it. I'd say, "I have a **new system** that'll help us collaborate more effectively." Well, when you say *"new,"* people hear *"change,"* and they realize that means *"more work,"* at least in the short run. And when you say *"system,"* people hear *"IT,"* and they know that means, *"someone else's responsibility."* So when you say *"new system,"* what people **really** hear is *"more work that shouldn't be my responsibility in the first place."* Not exactly an appealing message. - [View Highlight](https://read.readwise.io/read/01h12gtcrj4ebnet35rwg23ndz) --- > I had to lay the "hard" groundwork to initiate the project, but my sustained focus on the strategic plan, the structure, and the system actually delayed our progress, and the wiki's ultimate success is directly related to its integration with the organization's "soft" side. - [View Highlight](https://read.readwise.io/read/01h12gxmg7ncg2jc9bvmxt96zh) ---