公司讓微信加人有沒有軟件_沒有人想要使用軟件

公司讓微信加人有沒有軟件

為什么您應該重新考慮軟件開發 (Why you should rethink software development)

Today, software is everywhere. Modern society depends on it. It’s inside watches, medical devices, phones, TVs, elevators, cars, and even “computers” (as if those other things don’t compute.)

如今，軟件無處不在。現代社會依賴于此。它位于手表，醫療設備，電話，電視，電梯，汽車甚至“計算機”內部(就像其他東西無法計算一樣)。

As a consultant, I’ve helped companies develop software for the past 14 years, and coded quite a bit of software myself.

作為顧問，我在過去的14年中一直幫助公司開發軟件，并且自己編寫了很多軟件。

I co-authored an international standard and worked with adopters to implement it. I wrote software that controlled the behavior of a satellite communication system. I developed tools for a team that created a model of the European Extremely Large Telescope. I was involved with software for automotive companies, healthcare systems, banks, insurance, telecommunications, aviation and more.

我與人合著了國際標準，并與采用者一起實施。我寫了控制衛星通信系統行為的軟件。我為一個團隊開發了工具，該團隊創建了歐洲超大型望遠鏡的模型。我參與了汽車公司，醫療保健系統，銀行，保險，電信，航空等領域的軟件開發。

In some of these companies, software development worked well. Teams delivered software in high quality. Stakeholders were happy. The companies grew their customer base, and ultimately their profit.

在其中一些公司中，軟件開發效果很好。團隊提供了高質量的軟件。利益相關者很高興。這些公司擴大了客戶群，最終增加了利潤。

But other companies struggled.

但是其他公司苦苦掙扎。

I saw departments fighting each other over whose requirements to include in a release.

我看到部門在為發布中包含誰的要求而相互爭斗。

I saw developers who could not keep up with the amount of feature creep and change requests. Some of them lost any sense of purpose in what they were building.

我看到開發人員無法跟上功能的不斷變化和變更請求的數量。他們中的一些人在建造房屋時失去了目標感。

I watched as communication broke down between developers and the non-technical business stakeholders who managed them.

我看到開發人員與管理他們的非技術業務利益相關者之間的交流中斷了。

And after a few years, I recognized a pattern.

幾年后，我意識到了一種模式。

Whenever people asked me what was going wrong, I just started telling them: nobody wants to use software.

每當有人問我出了什么問題時，我就開始告訴他們： 沒有人愿意使用軟件。

At first, they looked at me like I was crazy. Software is everywhere. It’s what powers modern civilization! But after I explained myself, many of these same people would slowly nod in somber agreement.

一開始，他們看著我就像我瘋了一樣。軟件無處不在。這就是現代文明的力量！但是，在我向自己解釋之后，許多同樣的人會慢慢地以含糊的同意地點頭。

If you are like me, you do at least some of your shopping online.

如果您像我一樣，則至少會在網上進行一些購物。

Do you want to register for one more e-commerce website?

您是否要注冊一個電子商務網站？

Do you enjoy adding products to your shopping cart, one by one?

您喜歡將產品逐一添加到購物車嗎？

Do you want to double-check whether the credit card number you entered is correct?

您是否要仔細檢查您輸入的信用卡號是否正確？

Do you want to confirm your purchase several times?

您是否要多次確認購買？

I sure don’t.

我當然不會。

But still, I shop online. Why?

但是我還是在網上購物。為什么？

達到理想的結果 (Reaching the desired outcome)

What I want is a desired outcome: I want to own a new washing machine or read a new book. Every interaction between me and the software is a step between me and that outcome.

我想要的是一個理想的結果 ：我想擁有一臺新洗衣機或讀一本新書。我與軟件之間的每一次互動都是我與結果之間的一步。

Recognizing this has had a huge impact on the way I develop software.

認識到這一點對我開發軟件的方式產生了巨大的影響。

Many companies measure developer productivity by lines of code or by velocity, which roughly means: completed features per time, adjusted by feature size.

許多公司通過代碼行或速度來衡量開發人員的生產力，大致表示：每次完成的功能，由功能大小調整。

Some people think selling features is like selling oranges. The more features you provide to customers, the higher the profit.

有人認為賣功能就像賣橘子。您提供給客戶的功能越多，利潤就越高。

But I’m here to tell you that it isn’t.

但是我在這里告訴你事實并非如此。

Adding more features may make it easier or harder for your user to reach their desired outcome. It may actually stand in the way. There are other, more useful metrics than velocity.

添加更多功能可能使您的用戶更容易或更難達到所需的結果。它實際上可能會妨礙您。還有其他比速度更有用的指標。

When you enter a new market, make sure that your software fulfills some customer need. Cherish your customers and get frequent feedback. Don’t turn your software in a bloated, feature-rich mess that nobody wants to use.

當您進入新市場時，請確保您的軟件能夠滿足某些客戶需求。珍惜您的客戶并獲得頻繁的反饋。不要把軟件變成in腫，功能豐富的混亂局面，沒人想使用。

If you already have a solid position in a market, clear the way. Make a user’s journey to their desired outcome as short and pleasant as possible. Because the end of that journey is the first moment value is created for your company.

如果您已經在市場上占有一席之地，請清除道路。使用戶的旅程盡可能短而愉快。因為旅程的終點??是為公司創造價值的第一刻。

If you can get users to complete their journeys to the desired outcome with less steps, good. Develop less, because software development is an investment.

如果您可以使用戶以更少的步驟完成他們的旅程，以獲得理想的結果，那很好。減少開發，因為軟件開發是一項投資。

亞馬遜的Kindle如何縮短旅程 (How Amazon’s Kindle shortens the journey)

Amazon started out selling books online. You went there to buy a book, which they’d ship to your door.

亞馬遜開始在網上銷售書籍。您去那里買了一本書，他們將它們運到您家。

Then they pioneered 1-Click payment, so you could skip entering your payment details and clicking through a shopping cart funnel each time you wanted to buy something. This shortened the user journey.

然后，他們開創了1-Click付款的先河，因此您可以在每次要購買商品時跳過輸入付款明細并單擊購物車漏斗的過程。這縮短了用戶旅程。

Later, they introduced the Kindle. This further shortened the user journey. Find a book, view its details, confirm the purchase. After a short download, you’ve got the book. No more waiting for shipping.

后來，他們推出了Kindle。這進一步縮短了用戶旅程。查找一本書，查看其詳細信息，確認購買。短暫下載后，您已經掌握了這本書。無需等待運送。

Ultimately, all of this leads to the same outcome as in the early days of Amazon: you can read a book.

最終，所有這些都導致了與亞馬遜成立初期相同的結果：您可以閱讀一本書。

It’s just that now the journey taken to get there is a whole lot shorter.

只是現在到達那里的旅程要短得多。

Developing as many features as possible is not enough to be successful. Fortunately, I am not the only one who thinks that.

開發盡可能多的功能不足以成功。幸運的是，我并不是唯一一個這么認為的人。

Gojko Adzic created Impact Mapping, a technique for deriving software features from business goals. He asked the developer community to “Make impacts, not software.”

Gojko Adzic創建了Impact Mapping ，這是一種從業務目標中獲取軟件功能的技術。他要求開發人員社區“ 產生影響，而不是軟件。”

David Heinemeier Hansson, creator of Ruby on Rails, believes that you can always do less.

Ruby on Rails的創建者David Heinemeier Hansson認為您總可以做得更少。

As much sense as this makes to the developers I explain this to, in my experience, only a minority of companies have put this philosophy of shortening user journeys into practice.

就這對開發人員的意義而言，根據我的經驗，我只向少數公司解釋了這種縮短用戶使用時間的理念。

So don’t get me wrong: I love software. I’m fascinated by it. I started developing software in the early 90s, and I’m still into it.

所以請不要誤會我：我喜歡軟件。我被它迷住了。我于90年代初開始開發軟件，現在仍然投入其中。

Software is useful. But not on its own. Software is just a means to an end.

軟件是有用的。但不是靠它自己。軟件只是達到目的的一種手段。

Please keep that in mind.

請記住這一點。