Beyond RFPs: 3 keys to finding the best software vendor

本文探讨了在选择软件供应商时超越传统RFP流程的方法,强调寻找那些关注业务成果而非仅仅技术部署的合作伙伴。文章提出了三个关键特性:关注大局、减少过程摩擦及以人为本的态度。



I talked in my last blog post about the ideal customer-vendor relationship, which I believe should be a partnership focused not on technology deployment but on tangible business outcomes that move your company forward. To achieve that kind of relationship, you need to look beyond line items on an RFP or RFQ at the type of approach the vendor takes to the market.  Look for three must-have characteristics: A focus on the bigger picture, a minimal friction approach, and an orientation that favors people over process.


my way sign    Look for a vendor with a collaborative approach.Focused on the bigger picture

First and foremost, you want a vendor that is focused on making their customers successful. They are not going to be focused on time and materials, or on how much money they make up front. They are going to be focused on getting you to a mutually agreed upon result.

 

That means both parties need to think bigger. You need to think, is this a comprehensive solution or is it a stopgap for a certain business function? The vendor should be thinking that way too, drilling down into your business to find out whether solving this one problem is going to do it for you.

 

There are plenty of people that create great stopgaps for individual business functions. There aren’t too many vendors that are thinking holistically about the customer’s business outcome.

 

To take an example from our industry, there are vendors out there that automate the invoice approval process and they do a great job of it and Accounts Payable departments are delighted.  The invoice comes in, it’s $500, they pay it in 24 hours and they feel proud of that great turn-around time.

 

What they sometimes don’t know is whether or not anyone even ordered the item, whether they ever received the item or whether or not the item was needed.  In fact, even if the employee might have perceived the item as necessary, it might be for a project that is counter to the strategy of the company. Now, as for AP, they just feel good because they managed the invoice. It’s a broken process.

 

Or take another process in our industry--expense reports. We used to have all this paper coming in, and now we’ve automated expense reports and everything now that used to be paper is managed through the expense reporting system.

 

That does nothing for spend management; people could be spending more money because they’re traveling more, they may be staying at more expensive hotels, or doing things that aren’t necessarily required by the company. Where is the pre-approval process for certain categories of spend? That hasn’t even been touched, but you automated the expense report process and you feel good about yourself as a controller. Again, you didn’t solve the broader business issue.

 

Anybody can automate something for you. Look for a vendor focused on business outcomes and results, one that has people internally who understand how to solve your business problems, not just meet your technology requirements.

 

A minimal friction approach

The ideal vendor is not looking to “process” anything. They’re looking for the most straight-line path to results for the customer. To me that means finding places to remove friction, and not introducing additional friction into any process that already exists.

 

What does that look like? Crappy company A comes in and says, “you will have to adopt our tool, roll out training, have people go to this site to do this, follow this procedure to achieve this,” and on and on.  It’s like, “we’re coming in with the technology, and everybody watch out and learn how to do it our way.” Seriously.

 

That is the old way. It’s like taking a VCR out of the box in 1995. Big manual, blue screen, trying to figure out how to record a Seinfeld episode, and it takes 2 hours to do it for your grandparents. Nobody knows how to do it and everyone hates it. That’s option A.

 

Company B comes in with minimal friction. They try to weave themselves into the existing business processes that are happening in the organization. In our industry, examples of weaving in would be, approvals done on a mobile device, visibility into budget, or push notifications on a mobile device. User says,  “Oh there’s something here, I guess I gotta approve the marketing event or promotion that we’re about to kick off .” They press a button and they do it. There’s no training, there’s no learning curve. It’s right there.

 

Company B asks, “How are things running today? How do you conduct business today? How do your expense reports come in today? What are you using for that? How are you sending purchase orders to suppliers today? Is it via fax, is it via a PDF in an email?”

 

Company B listens to you and says, “Great! We can look to incorporate that same process and transition you onto our system.” They’re thinking from a change management perspective, thinking about what it takes to go from a person’s process today to the process tomorrow while understanding people’s natural resistance to change. That’s the big difference, the focus on the result, not the process.

 

It’s like when you take an Apple product out of the box. There is no manual. It just says, “Made in California” and you turn it on.  You learn the way you learn to ride a bike. You just start riding it, vs. reading and referring to section 2.6 on page 59.

 

People over process

That brings me to the third point: Look for a company that is malleable, understands human interaction, understands that it’s 2013, and looks to consistently improve in the way it’s working.

 

Listen to how they speak. Is it, “Version 6.12 requires you to log into this screen, or call this phone number?” Is it like getting on certain airlines, where you’re about to board the plane but since you’re elite level titanium plus-plus you get to board the plane 2 seconds before this other person? What these companies are saying is, we have rigid, bureaucratic processes and this is how we work so this is how you work.

 

A people-oriented company questions processes and uses common sense to adjust. It’s not afraid to fall on its own sword and say, “we screwed this up, we gotta get better.”

 

One company tries to lay down the law. The other is willing to have a dialog with you and adapt based on the your feedback.  It’s an organism that’s evolving in real time.  It’s the difference between a plant that’s growing, and a computer monitor that’s going to be the same in 30 years no matter what I do to it.

 

This is how you notice the difference between vendors. You have to go beyond the RFP and the technology requirements and listen to how they talk and look at how they do things. If you’re looking to partner with a vendor to solve your business problems and not create new ones, look for one that’s gonna focus on getting you to a level of business success, not just implementing some technology.

 

Look for one that’s going to achieve results through a transition process that understands that it takes something to go from today to the future state and helps transition you over, and thirdly one that’s adaptive, that strives for excellence in everything it does vs. a “my way or the highway” kind of approach.

内容概要:本文档是一份关于交换路由配置的学习笔记,系统地介绍了网络设备的远程管理、交换机与路由器的核心配置技术。内容涵盖Telnet、SSH、Console三种远程控制方式的配置方法;详细讲解了VLAN划分原理及Access、Trunk、Hybrid端口的工作机制,以及端口镜像、端口汇聚、端口隔离等交换技术;深入解析了STP、MSTP、RSTP生成树协议的作用与配置步骤;在路由部分,涵盖了IP地址配置、DHCP服务部署(接口池与全局池)、NAT转换(静态与动态)、静态路由、RIP与OSPF动态路由协议的配置,并介绍了策略路由和ACL访问控制列表的应用;最后简要说明了华为防火墙的安全区域划分与基本安全策略配置。; 适合人群:具备一定网络基础知识,从事网络工程、运维或相关技术岗位1-3年的技术人员,以及准备参加HCIA/CCNA等认证考试的学习者。; 使用场景及目标:①掌握企业网络中常见的交换与路由配置技能,提升实际操作能力;②理解VLAN、STP、OSPF、NAT、ACL等核心技术原理并能独立完成中小型网络搭建与调试;③通过命令示例熟悉华为设备CLI配置逻辑,为项目实施和故障排查提供参考。; 阅读建议:此笔记以实用配置为主,建议结合模拟器(如eNSP或Packet Tracer)动手实践每一条命令,对照拓扑理解数据流向,重点关注VLAN间通信、路由选择机制、安全策略控制等关键环节,并注意不同设备型号间的命令差异。
多旋翼无人机组合导航系统-多源信息融合算法(Matlab代码实现)内容概要:本文围绕多旋翼无人机组合导航系统,重点介绍了基于多源信息融合算法的设计与实现,利用Matlab进行代码开发。文中采用扩展卡尔曼滤波(EKF)作为核心融合算法,整合GPS、IMU(惯性测量单元)、里程计和电子罗盘等多种传感器数据,提升无人机在复杂环境下的定位精度与稳定性。特别是在GPS信号弱或丢失的情况下,通过IMU惯导数据辅助导航,实现连续可靠的位姿估计。同时,文档展示了完整的算法流程与Matlab仿真实现,涵盖传感器数据预处理、坐标系转换、滤波融合及结果可视化等关键环节,体现了较强的工程实践价值。; 适合人群:具备一定Matlab编程基础和信号处理知识,从事无人机导航、智能控制、自动化或相关领域研究的研究生、科研人员及工程技术人员。; 使用场景及目标:①应用于多旋翼无人机的高精度组合导航系统设计;②用于教学与科研中理解多传感器融合原理与EKF算法实现;③支持复杂环境下无人机自主飞行与定位系统的开发与优化。; 阅读建议:建议结合Matlab代码与理论推导同步学习,重点关注EKF的状态预测与更新过程、多传感器数据的时间同步与坐标变换处理,并可通过修改噪声参数或引入更多传感器类型进行扩展实验。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值