如何開發一個hexo主題

by Cameron Jenkinson

卡梅倫·詹金森(Cameron Jenkinson)

如何確定一個強烈的主題可以使產品開發更有效 (How identifying a strong theme can make product development more effective)

MVPs always seem easy to execute and build. The first version is shipped with a few features and development is simple to manage.

MVP似乎總是易于執行和構建。 第一個版本附帶了一些功能，并且開發易于管理。

This simplicity affords a focus that is disciplined and strong, because those initial features stand for the core idea.

這種簡單性提供了紀律嚴明且重點突出的焦點，因為這些初始功能代表著核心思想。

However, as an idea grows, so do its changing product priorities and ever increasing customer feedback demanding change. What was once a simple product vision can become something verbose. You can lose sight of what made it mean something to people in its initial simplicity.

但是，隨著想法的發展，其不斷變化的產品優先級以及不斷增加的要求變化的客戶反饋也在不斷發展。 曾經簡單的產品愿景可能會變得冗長。 您可能忽略了最初使它對人們有意義的東西。

問題 (The Problem)

Technology companies typically have either a top-down or bottom-up approach to product development.

技術公司通常對產品開發采用自上而下或自下而上的方法。

A top-down focus usually means that leadership directs all product decisions. A bottom-up focus is driven entirely by research and feedback.

自上而下的關注通常意味著領導者將指導所有產品決策。 自下而上的重點完全由研究和反饋驅動。

Beauty lies somewhere in between, when these two approaches are taken together. But when one weighs in more, problems start to occur.

當這兩種方法結合在一起時，美就介于兩者之間。 但是，當一個人承擔更多責任時，就會開始出現問題。

自上而下的焦點 (Top down focus)

Characteristics of a top-down approach to product development typically look like this:

自上而下的產品開發方法的特征通常如下所示：

• Investors tell leadership what to tell the product teams to build
  投資者告訴領導要告訴產品團隊的內容
• Investors and leadership hold meetings where they make decisions about the product without a lead product team member present
  投資者和領導層舉行會議，在沒有首席產品團隊成員出席的情況下就產品做出決策
• Leadership team gives the product team a list of features they want to be built
  領導團隊為產品團隊提供了他們想要構建的功能列表
• Leadership changes sprints mid-way through because they want something added or changed immediately
  領導力改變是在中途進行的，因為他們希望立即添加或更改某些東西
• Leadership plans sprints and directs the product roadmap, whereas the product team simply executes with no involvement in those decisions
  領導力計劃沖刺并指導產品路線圖，而產品團隊只是執行而無需參與這些決策

自下而上的焦點 (Bottom up focus)

On the other side, a bottom-up approach usually looks like this:

另一方面，自下而上的方法通常如下所示：

• Leadership stays out of product development in general and focuses on setting business priorities in the form of goals, visions, and strategies
  領導力通常不會影響產品開發，而是專注于以目標，愿景和策略的形式設置業務優先級
• Leadership has frequent meetings about the direction of the product with suggestions in hand, but typically accepts push back on their suggestions from product team leads
  領導層經常召開有關產品方向的會議并提出建議，但通常會接受產品團隊負責人的建議
• Leadership makes suggestions, but the product team leads always have the final call
  領導提出建議，但產品團隊負責人始終擁有最終決定權
• Leadership avoids and rarely engages with individuals in the product team (designers, developers, and so on)
  領導力避免和很少與產品團隊中的人員(設計師，開發人員等)互動

Any of this sound familiar?

這些聽起來很熟悉嗎？

These characteristics can paint a picture of any product development environment at a startup in the last few years.

這些特征可以描繪最近幾年初創公司中任何產品開發環境的情況。

So what is the problem with all of this?

那么所有這一切有什么問題呢？

It comes down to communication.

歸結為溝通。

The communication of ideas about how to make the product better while keeping it in line with the original vision.

交流有關如何使產品更好，同時又與最初的愿景保持一致的想法。

People generally don’t like confrontation. Depending on how top-down or bottom-up the environment is, the degree of honesty people display is going can be vastly different.

人們通常不喜歡對抗。 根據環境自上而下或自下而上的程度，人們所表現出的誠實程度可能會大不相同。

This is because people don’t like to know that their ideas and suggestions aren’t very good … and people don’t like to tell people that their ideas and suggestions aren’t very good.

這是因為人們不喜歡知道他們的想法和建議不是很好。。。人們不喜歡告訴人們他們的想法和建議不是很好。

When this honesty isn’t enforced and managed, it can take the original product vision on a rollercoaster ride of changes. These changes are sometimes hard to spot in the beginning, but can result in disasters over the long term.

如果不執行和管理此誠實原則，則可以將原始產品愿景帶入過山車般的變革之路。 有時一開始很難發現這些變化，但從長期來看可能會導致災難。

解 (Solution)

產品主題 (Product themes)

Product themes are the gatekeepers that are summoned to protect the team’s focus and make communication between people more honest.

產品主題是守門員，它們被召喚來保護團隊的注意力并使人與人之間的溝通更加誠實。

Product themes sit at the table when people are talking and making decisions about the product.

當人們在討論產品并做出決定時，產品主題就擺在桌面上。

You can think of themes like the secret service or the armed guard. They have sworn an oath to protect the team’s focus from being hurt, lost, or altered in any way.

您可以想到諸如特勤局或武裝警衛等主題。 他們宣誓要保護團隊的焦點不受傷害，丟失或以任何方式改變。

Instagram used themes, and we can all agree that they’ve done pretty well to keep their product under control.

Instagram使用了主題，我們都可以同意他們在控制產品方面做得很好。

“In the early days of Instagram, Krieger and his team recorded their action items in a rolling Google Doc, organized by themes.” — Source

“在Instagram成立之初，Krieger和他的團隊將主題活動記錄在按主題組織的滾動Google Doc中。” — 來源

Product themes act as a negotiator between people, because they interject and help facilitate people’s ideas about or related to product development.

產品主題充當人與人之間的談判者，因為它們插入并幫助促進人們關于產品開發或與產品開發有關的想法。

“One of our themes was being the fastest photo-sharing app in the world. What are we working toward within that theme? Next, we wanted to make the photos look incredible, way beyond what you’d expect from a cell phone. What are we doing on that? Anything that didn’t fit into those things went by the wayside. “ — Mike Krieger, Instagram“我們的主題之一是成為世界上最快的照片共享應用程序。 在該主題下，我們正在做什么？ 接下來，我們希望使照片看起來令人難以置信，遠遠超出了手機的預期。 我們在做什么呢？ 任何不適合這些事情的東西都被拋在了一邊。 “ — Mike Krieger，Instagram

“Anything that didn’t fit into those things went by the wayside” — this is the important piece here.

“不適合這些事情的任何事情都被順便了” – 這是 這里的重要內容。

Instagram used themes to keep their focus in check.

Instagram使用主題來控制他們的注意力。

It would’ve been easy for the Instagram team to hold a meeting and accept suggestions. But these suggestions could have taken them away from the focus of “becoming the fastest photo sharing app in the world” if that theme wasn’t defined clearly before.

Instagram團隊召開會議并接受建議可能很容易。 但是，如果以前沒有明確定義主題，這些建議可能會使他們脫離“ 成為世界上最快的照片共享應用程序 ”的重點。

This is because communication generally has the most impact on focus during meetings. People easily impart views based on assumptions that can lead their focus astray or down another path.

這是因為交流通常在會議期間對焦點的影響最大。 人們很容易根據可能導致他們的焦點誤入歧途或沿著另一條道路前進的假設來發表觀點。

Imagine if Instagram did not have that theme at the core of what they were building, and instead took suggestions as they went along (like in an Agile environment).

想象一下，如果Instagram在其構建的核心中沒有該主題，而是在發展過程中采納了建議(例如在敏捷環境中)。

What if they looked at what people wanted at the time — adding more granular photo editing tools — and tried to implement that? Perhaps Instagram would have been closer to what Adobe Photoshop is.

如果他們查看了當時人們想要的東西-添加了更詳細的照片編輯工具-并試圖實現了該怎么辦？ 也許Instagram會更接近Adobe Photoshop。

But instead, their product themes protected this from happening. They ensured that the communication between team members was kept on track. And people didn’t have to feel like they were being swept aside or not valued by their team. It wasn’t Mike who said an idea wasn’t good. He used the themes to justify his opinions, so there was little confrontation.

但是，相反，他們的產品主題可以防止這種情況的發生。 他們確保團隊成員之間的溝通保持正常。 人們不必覺得自己被團隊排斥或不重視。 不是邁克說一個主意不好。 他使用主題來證明自己的觀點是正當的，因此幾乎沒有對抗。

Essentially, product themes give people permission to tell any team member that what they are saying is distracting the team from the core focus.

從本質上講，產品主題使人們可以告訴任何團隊成員他們的言論正在分散團隊對核心關注的注意力。

主題來自哪里？ (Where do themes come from?)

Product themes come from the creators beliefs about life or the problem they are trying to solve.

產品主題來自創作者對生活或他們要解決的問題的信念。

Themes have depth and are often rooted in strong beliefs about what should be true about a product or its impact on the world.

主題具有深度，并且通常植根于對產品或其對世界的影響應具有的真實信念。

A theme is a big idea, and it usually touches on human experiences that everyone can relate to (so they are not technical descriptions).

主題是一個很大的主意，通常涉及每個人都可以涉及的人類經驗(因此，它們不是技術描述) 。

他們如何工作 (How they work)

To create a product theme, you must come up with a set of statements that embody strong beliefs and convictions about the product itself.

要創建產品主題，您必須提出一組陳述，這些陳述體現出對產品本身的強烈信念和信念。

Instagram’s main theme was: “to be the fastest photo sharing app in the world.”

Instagram主要主題是：“ 成為世界上最快的照片共享應用程序 。”

This is strong assertion and a clear message that has depth. People looking at Instagram today and would probably say that it embodies that theme.

這是強有力的主張，是一條具有深度的明確信息。 今天在看Instagram人們可能會說它體現了這一主題。

Instagram’s users support and drive that theme when using it without even thinking it about it — the theme is in the product’s DNA.

Instagram用戶在使用該主題時就支持并推動該主題，而無需考慮它-該主題存在于產品的DNA中。

When a team is having discussions, planning the execution of the product, this theme must be present and “at the table” with them every day. While the theme is present, it permits the team to discuss only ideas and information that make that theme become a reality.

當團隊進行討論并計劃產品的執行時，必須每天與這個主題一起“出現在餐桌上”。 存在主題時，它允許團隊僅討論使該主題變為現實的想法和信息。

I guess you could think of a theme as spirit that wants to live in the real world.

我想您可以將主題視為想要生活在現實世界中的精神。

It wants you to make it real and protect it from being anything other than what it wants to be.

它希望您使其成為現實，并保護它免受其自身的影響。

This is why I believe product themes can be a simple framework that protects the team’s focus and makes the way we build products more inclusive and effective.

這就是為什么我認為產品主題可以是一個簡單的框架，可以保護團隊的注意力，并使我們構建產品的方式更具包容性和有效性。

如何使用 (How to use them)

In order to take a structured approach when using product themes, you must first adopt the mindset of Shipping VS Learning. In this mindset, teams prioritize learning as a regular deliverable over shipping stuff. This is the underlying method that guides how product themes can be used to drive product decisions.

為了在使用產品主題時采取結構化的方法，您必須首先采用Shipping VS Learning的思維方式。 在這種思維方式下，團隊優先將學習作為常規交付物，而不是運送物資。 這是指導如何使用產品主題來推動產品決策的基礎方法。

Here are some things that can go wrong when teams ship stuff without product themes guiding them:

當團隊在沒有產品主題指導他們的情況下運送東西時，可能會出錯：

• Teams ship inferior or non-impactful products in order to say they shipped something
  團隊運送劣質或非不良品，以表示他們運送了一些東西
• Teams ship things that teach their company nothing
  團隊交付的東西對公司毫無幫助
• Teams aren’t given enough runway to do great work because of the constant pressure to ship ASAP
  團隊沒有足夠的跑道來完成出色的工作，因為要盡快運送

On the other hand, learning as quickly as possible and making sure that learning is prioritized is the most likely contribution to product success. Shipping is part of the learning process, but learning comes first.

另一方面，盡可能快地學習并確保學習被優先考慮是對產品成功的最有可能的貢獻。 運輸是學習過程的一部分，但學習是第一位的。

Sprint模板 (A Sprint template)

Here is what a theme-based sprint could look like over the course of 2 weeks:

在兩周的時間內，基于主題的sprint可能看起來像這樣：

• Product theme: make achieving any career change the easiest journey possible

  產品主題：實現任何職業轉變都是最輕松的旅程

• What we learned: Removing steps from our onboarding experience did not reduce user confusion. Instead, clearing up language such that users felt they were making progress resulted in the greatest gains (link to more details here).

  我們學到的知識：從我們的入職經驗中刪除步驟并不會減少用戶的困惑。 相反，清除語言以使用戶感到自己正在取得進步，從而獲得最大的收益(在此處鏈接到更多詳細信息)。

• Cost to learn: One researcher, one designer, and one week of their calendar time cost €200 in user participant fees.

  學習成本：一位研究人員，一位設計師和他們一周的日歷時間花費200歐元的用戶參與費。

• Plan to proceed: Productionize new language within one month.

  計劃進行：在一個月內產生新語言。

• What’s needed to proceed: Some internationalization help… we’ll outsource this.

  需要做什么：一些國際化幫助……我們將把它外包。

According to Shipping vs. Learning, What we learned is the key deliverable, and it’s something potentially interesting to many people across the company.

根據“運輸與學習”， 我們學到的是關鍵的交付成果，這對于公司中的許多人來說可能是一件有趣的事情。

Cost to learn is a chance to optimise for and highlight efficiency, as spending a year of engineering time carries much greater opportunity costs than running some efficient, qualitative testing.

學習成本是優化和突出效率的機會，因為花費一年的工程時間比運行某些有效的定性測試帶來更多的機會成本。

Plan to proceed lets people know the outcome of the learning and how it affects the way forward.

進行計劃使人們知道學習的結果以及它如何影響前進的道路。

And finally, what’s needed to proceed spells out what a manager, executive, or anyone outside the core team can do to help.

最后， 需要進行的工作闡明了經理，主管或核心團隊以外的任何人可以提供幫助的內容。

It can be very easy to spend weeks and weeks shipping product then learn absolutely nothing about how the product theme is going to be realized. This is why it’s so important to learn and spend time rethinking how people within the team approach learning and contributing to how product themes.

花數周和數周的時間來運送產品，然后完全不了解產品主題將如何實現，這可能非常容易。 這就是為什么學習和花時間重新思考團隊中的人們如何學習并為產品主題做出貢獻如此重要的原因。

Sprints should be organised by each of the product themes, where tasks follow whatever system you are already using. Incomplete tasks under each theme can be pushed along to another sprint, but the identity and purpose of every sprint is never lost.

Sprint應按每個產品主題進行組織，其中任務遵循您已經在使用的任何系統。 每個主題下未完成的任務可以推送到另一個sprint，但是每個sprint的標識和目的都不會丟失。

It isn’t about what are we shipping this week. It should become what can we learn this week to realise the product theme better than we did last week.

這與我們本周要發貨的產品無關。 與上周相比，本周我們應該可以學習到如何更好地實現產品主題。

結語 (Wrapping up)

In conclusion, when building a product it is imperative that a narrative is made around what the core themes are and how your team prioritises development efforts around them. Everyone within an organisation should be made aware of what the product themes are so that everyone has the opportunity to manage the overall development towards realising them.

總之，在構建產品時，必須圍繞核心主題以及團隊如何確定圍繞它們的優先級進行敘述。 組織中的每個人都應該了解產品主題是什么，以便每個人都有機會管理總體開發以實現它們。

Product themes are not an afterthought or something related only to the product’s department. They should be respected and managed just like a company vision or mission statement. I would even suggest that, in some cases, product themes are the foundation to a long lasting company statement of purpose.

產品主題不是事后的想法，也不只是與產品部門有關的東西。 他們應該像公司愿景或使命聲明一樣受到尊重和管理。 我什至建議在某些情況下，產品主題是公司持久目標的基礎。

翻譯自: https://www.freecodecamp.org/news/how-themes-simplify-product-development-b6bab1afd01d/

如何開發一個hexo主題

總結

以上是生活随笔為你收集整理的如何开发一个hexo主题_如何确定一个强烈的主题可以使产品开发更有效的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。