Skip to content

Home

  • in podcast
  • 3 min read

Jobs to Be Done

Host (Victor): Welcome to another episode of Continuous Improvement, the podcast all about personal and professional growth. I'm your host, Victor, and today we're going to dive into a thought-provoking topic: the importance of understanding the job to be done when using a product or service.

Have you ever encountered an error message during an online transaction that left you frustrated? Join the club! Today, I want to share a personal experience that made me realize how crucial it is for both vendors and customers to consider the task at hand before using a service or product.

In my previous role as a technical lead in a bank, I discovered something quite fascinating. The financial industry is filled with acronyms, and even the banks have their own cynical ones. For instance, the bank I worked for, HSBC, had an acronym that stood for "How Simple Becomes Complicated." It perfectly captures the complexity behind seemingly simple tasks, like pressing a button on an internet banking site.

The process of delivering these services involves multiple teams working together. The business team collects requirements, the design team creates the layout, and the development team writes, tests, and deploys the software. Believe it or not, it often takes up to two weeks just to make a tiny alteration to a webpage.

During my time as part of the ASD-ASP team, responsible for creating regional features, I had the opportunity to develop services like PayNet's FPX in Malaysia and PayNow in Singapore. I was proud of my work, making online transactions smoother for customers.

However, I soon realized that there was an important aspect I hadn't fully considered — accessibility. Imagine being visually impaired and relying on assistive tools to navigate a website. It never occurred to me that the tools would unknowingly interrupt the transaction process by constantly announcing the countdown of remaining time.

I wanted to address this issue, but it proved to be quite challenging in such a large organization. The business analysts were mainly concerned with profits and considered their job done. The designers focused more on flashy animations rather than considering accessibility, and the engineers were already looking ahead to explore emerging technologies like machine learning and blockchain.

Sigh I wish I had known about Aristotle's three modes of persuasion back then - Ethos, Logos, and Pathos. These powerful tools could have helped me advocate for change and show the importance of considering the needs of all users.

Now, I'd love to hear your thoughts on this matter. Before using a product or service, have you ever considered the job it is meant to accomplish? What improvements would you like to see in the services you use?

Clayton Christensen, a renowned professor from Harvard Business School, introduced the concept of understanding the job that a person hires a product to do. This understanding allows us to identify areas for improvement and create a better experience.

When I use online banking, my job is simply to complete the transaction. I don't care about flashy animations or the latest technologies. I want a smooth process that ensures successful transactions for everyone, including those with visual impairments. Did you know that in Malaysia, the government has regulations requiring a 70% success rate for FPX transactions, with penalties for non-compliance?

So, next time you encounter an issue with online banking or any other service, ask yourself: What is the job to be done? Think about others who may face similar challenges, especially those with different abilities. Don't forget, as a customer, you have a voice. Communicate your needs to the service providers and help drive positive change.

Remember, this is not a matter to be taken lightly. We each have the power to be the change we wish to see in the world.

That's all for today's episode of Continuous Improvement. I hope you found this discussion thought-provoking and that it inspires you to consider the job to be done when using products or services.

If you enjoyed this episode, don't forget to subscribe to our podcast and leave us a review. We always appreciate your feedback.

Until next time, keep striving for improvement in every aspect of your life. This is Victor, signing off.

[End of the podcast]

  • in zh
  • 1 min read

需要完成的工作

我確定你在網上購物時經歷過這種情況。你找到一個價格吸引的商品並決定購買它，使用網上銀行進行付款。然而，出現了一條錯誤信息說："對不起，出了點問題；交易失敗。請稍後再試。"這很煩人，對吧？也許你受夠了，決定放棄。但在你這樣做之前，考慮一下當你使用服務或產品時的"手頭任務"。這個問題對供應商和你都至關重要。

在過去，我曾在一家銀行擔任技術主管，我發現金融業充滿了縮寫。我以前工作的銀行匯豐，有一個相當諷刺的自稱："How Simple Becomes Complicated." 如果你認為在網上銀行網站上按一個鍵就很簡單，那你就錯了。這個過程非常復雜。商業團隊收集需求，設計團隊創建佈局，開發團隊撰寫，測試並部署軟件。平均而言，僅更改網頁上的一個字符就需要兩周的時間。

我是ASD-ASP團隊的一員，這意味著我在亞太地區負責加速規模交付，我負責的是創建區域功能。如果你來自馬來西亞，你無疑已經使用過PayNet的FPX（Financial Process Exchange）服務。在新加坡，一個相似的服務被稱為PayNow。

經過幾個月的辛勤工作，我創建了該功能並將其投入生產。我想："終於，我的工作完成了！"現在，當你在Shopee上購買耳機時，你可以選擇FPX作為付款方式。你在點擊"支付"按鈕後完成了購買，我對我的工作感到滿意。

然而，想像一下如果你是視障人士，依賴輔助工具來導航網站。你不會知道你只有10分鐘的時間可以完成交易。輔助工具會大聲讀出每一秒，倒數時間，讓你沒有時間完成你的任務。這是一個真正的痛點，我當時沒有考慮到。直到很久以後我才收到實際用戶的反饋。

我試圖解決這個問題，但在這樣一家大公司中幾乎不可能。我與商業分析師交談，他們說他們的工作已經完成了，因為他們主要關心的是利潤。設計師宣稱他們的工作已經完成，他們更喜歡創建華麗的動畫，而不是關注輔助功能。工程師們也堅持他們的工作已完成；他們想轉向機器學習和區塊鏈技術。

我無法說服我的同事，部分原因是我不瞭解亞里士多德的三種說服方式：Ethos、Logos和Pathos。但現在，我想聽聽你的想法。在你使用產品或服務之前，考慮一下它應完成的工作是什麼。

哈佛商學院的教授克雷頓·克里斯蒂森森（Clayton Christensen）闡述了這種方法。他的論文提出了問題："一個人僱用一種產品來完成什麼任務？"理解這個任務會使找出改善產品的方法變得更容易。

所以當我使用網上銀行時，我的工作就是完成交易。我不在乎華麗的動畫或者系統是否使用了AI或加密貨幣。產品團隊一直在問錯誤的問題，並嘗試解決錯誤的問題。我們必須超越競爭對手，確保所有人，包括視覺障礙者，都能成功交易。馬來西亞政府甚至有規定要求，FPX交易必須成功率達到70%，否則將面臨處罰。

工作還沒有完成，還有一頭大象在房間裡。下次你在網上銀行遇到問題時，問問自己：什麼是"需要完成的工作"？對那些面臨同樣問題的人，尤其是視障人士，表示同情。作為顧客，將你的需求告訴銀行。通過表達你的憂慮來推動變革。這個事情不容忽視。你要做你想在世界上看到的變化。

  • 3 min read

Working with Localization on Websites and Mobile Apps in APAC

First and foremost, why does this blog post exist? What question are we trying to answer? A colleague of mine in the UK specifically asked me about localization, tools, and best practices—or lack thereof—in the Asia-Pacific region.

Since my company has expanded to various locations in the APAC area, including Singapore, the Philippines, and Vietnam, I am here to discuss frontend localization.

You'll likely encounter the term "i18n" in frontend development. Ever wondered what the 18 represents? It’s not 18 different languages; it's the number of letters between the first 'i' and the last 'n' in the word "internationalization."

Before diving in, let me introduce myself. I used to work as a technical lead in a bank and am sharing my previous experiences in the banking sector—a field rife with acronyms. You'll quickly realize that everything in banking involves an acronym, seemingly to sound more professional and obfuscate meaning.

I worked for HSBC, an acronym that humorously stands for "How Simple Becomes Complicated." Changing even a single character on a website is far from straightforward. The complicated process involves multiple teams—from business requirements to code review, quality assurance, and deployment—often taking up to two weeks just to change one word on a production webpage.

I was part of a team called ASD-ASP, which stands for Accelerated Scaled Delivery in the Asia-Pacific. My role involved building regional features for web and mobile platforms, such as FPX in Malaysia and PayMe for businesses in Hong Kong. The examples I mention are drawn from real-life experiences.

For instance, let's consider the page displayed below:

Notice anything wrong? The issue lies with the timer. Imagine being visually impaired and relying on an accessibility tool to navigate the page. You would be clueless about the remaining time to complete the transaction. Worse still, if you try to have the tool read the timer aloud, it will count down every second, leaving you no time to complete the transaction.

We used Adobe Experience Manager (AEM) to build this page. While AEM allows non-technical team members to make updates, the reality often involves frontend engineers making text changes or building dialogues using XML, creating an unnecessary layer of work.

In terms of mobile, our internal tools written in Python scripts read copy in various languages from a Confluence page to generate localized JSON files. The developer then includes this file in the app. This approach often creates more problems than it solves, as I'll explain shortly.

The copy team usually labels frontend designs using a Confluence page. This can easily go awry, as design screenshots often become outdated and engineers might use inconsistent keys to represent the same thing. Reusing keys across different pages leads to unexpected side effects when values are updated.

Next, consider the screen below for potential localization issues:

Here are five major pitfalls:

  1. The term "country" can be problematic. For instance, listing Taiwan or Hong Kong as separate countries can be illegal due to national security laws.

  2. Failing to localize the search bar is another issue. Search behavior and sorting algorithms vary between languages and regions.

  3. Error messages also need localization, not just translation. It's better to map error codes to localized messages instead of translating entire strings.

  4. Lack of versioning for translations can be disastrous, especially when business requirements change frequently.

  5. Ignoring accessibility translations can be detrimental to the user experience, especially for visually impaired individuals.

Furthermore, machine translations like Google Translate are highly discouraged. For more successful localization, collaborate with local teams who can readily identify potential issues.

Any questions about localization? Feel free to ask. :)

  • in podcast
  • 3 min read

Working with Localization on Websites and Mobile Apps in APAC

Welcome back to another episode of Continuous Improvement, the podcast where we explore strategies, best practices, and insights to help you enhance your professional skills. I'm your host, Victor, and today we're diving into the world of frontend localization.

But before we get started, let me share a bit about myself. I used to work as a technical lead in a bank, where acronyms seemed to rule the day. From HSBC, which hilariously stood for "How Simple Becomes Complicated," to ASD-ASP, the team I was part of—Accelerated Scaled Delivery in the Asia-Pacific—I learned firsthand how complex frontend development can be.

In today's episode, we'll be addressing a question from a colleague in the UK who reached out to me about localization, tools, and best practices in the Asia-Pacific region. With my company expanding to locations like Singapore, the Philippines, and Vietnam, it's a topic close to my heart.

So, let's start by demystifying the term "i18n" often used in frontend development. Did you ever wonder what the number "18" represents? Well, it's not actually about 18 different languages, but the number of letters between the first 'i' and the last 'n' in the word "internationalization."

Now, let's dive into some real-life experiences. During my time at HSBC, we faced numerous challenges when it came to making even the smallest changes on a website. It often took weeks to change just one word on a production webpage due to the involvement of multiple teams, from business requirements to code review, quality assurance, and deployment.

One example I encountered was a timer that posed serious accessibility issues. Imagine relying on an accessibility tool as a visually impaired user, and you have no way of knowing the remaining time to complete a transaction. It's a frustrating experience that could've been easily avoided through better frontend development practices.

Speaking of practices, we used Adobe Experience Manager (AEM) to build web pages. While it allowed non-technical team members to make updates, it frequently required frontend engineers to make text changes or create dialogues using XML—a process that added unnecessary complexity.

Mobile localization had its own set of challenges. We relied on Python scripts to read copy in various languages from a Confluence page and generate localized JSON files, which were then included in the app. However, this approach often created more problems than it solved, as we discovered.

One common issue was inconsistencies in frontend designs labeled using Confluence pages. Outdated screenshots and inconsistent keys caused unexpected side effects when values were updated. It's crucial to have a robust system in place to ensure accurate and up-to-date translations.

Let's now turn our attention to potential localization issues on-screen. Imagine a scenario where the term "country" is used to list Taiwan or Hong Kong as separate countries, which can be illegal due to national security laws. These are the kind of pitfalls that must be avoided in a robust localization strategy.

Another challenge is failing to localize the search bar. Search behavior and sorting algorithms vary across languages and regions, making it essential to adapt the functionality accordingly. Error messages also need proper localization and not just direct translation. Mapping error codes to localized messages proves more effective than translating entire strings.

Moreover, the lack of versioning for translations can be disastrous, particularly when business requirements change frequently. And let's not forget the importance of accessibility translations. Ignoring them can significantly harm the user experience, especially for visually impaired individuals.

While machine translations like Google Translate might seem tempting, they often fall short in accurately conveying the intended meaning. That's why collaborating with local teams who understand the cultural nuances and potential issues is crucial for successful localization.

I hope this discussion has shed light on the challenges and best practices involved in frontend localization. If you have any questions or want to share your experiences, feel free to reach out. Thanks for tuning in today, and remember, there's always room for continuous improvement.

  • in zh
  • 1 min read

在亞太地區的網站和移動應用上進行本地化工作

首先，為什麼這篇部落格文章會存在？我們試圖回答什麼問題呢？我在英國的一位同事特別問我關於在亞太地區的本地化、工具，以及最佳實踐——或者說沒有這樣操作的原因。

由於我的公司已經擴展到亞太區的多個地方，包括新加坡、菲律賓，和越南，我在這裡討論前端的本地化。

你可能會在前端開發中遇到「i18n」這個詞。曾經搞不清楚18代表什麼嗎？其實並非代表18種不同的語言；它指的是「internationalization」一詞中第一個i和最後一個n之間的字母數量。

讓我先自我介紹一下。我曾經在一家銀行擔任技術領導，現在想要分享我在銀行業的一些過去經驗——一個充滿縮寫詠詠的領域。你很快會意識到，銀行業的一切似乎都和縮寫有關，這看起來更專業，也使意思更為混淆。

我曾為HSBC工作，這是一個笑話般的縮寫，意思是「如何把簡單的事情變得複雜」。在網站上改變甚至一個字符也遠遠不是一件簡單的事情。複雜的過程涉及多個團隊——從商業需求到代碼審查，品質保證，和部署，往往需要花費兩個星期的時間來改變產品網頁上的一個詞語。

我是一個叫做ASD-ASP的團隊的其中一部分，這代表在亞太地區的加速規模化交付。我的角色涉及為網站和移動平台構建區域特性，比如在馬來西亞的FPX和在香港的商業PayMe。我提到的例子都是來自真實生活的經驗。

例如，讓我們考慮下面顯示的頁面：

注意到什麼問題了嗎？問題在於計時器。如果你的視覺有障礙，並且依賴訪問工具來導航網頁，你將對剩餘完成交易的時間一無所知。更糟糕的是，如果你嘗試讓工具將計時器大聲朗讀出來，它將每秒倒數，讓你沒有時間來完成交易。

我們使用Adobe Experience Manager (AEM)來構建這個頁面。雖然AEM允許非技術的團隊成員進行更新，但實際情況通常涉及到前端工程師進行文字更改或用XML構建對話框，創建了不必要的工作層。

在移動方面，我們的內部工具用Python腳本從Confluence頁面讀取各種語言的副本，以生成本地化的JSON文件。開發者然後在應用程序中包含此文件。這種方法常常會創建出比解決的問題更多的問題，我馬上就會解釋。

副本團隊通常使用Confluence頁面來標籤前端設計。這很容易出錯，因為設計截圖往往會過時，而工程師可能使用不一致的鍵來代表同一件事情。在不同頁面上重複使用鍵當值被更新時，會導致意外的副作用。

接下來，考慮下面的螢幕可能會遇到的本地化問題：

這裡有五個主要的陷阱：

  1. "country"這個詞可能會有問題。例如，因為國家安全法，列出台灣或香港作為單獨的國家可能是非法的。

  2. 沒有本地化搜索欄也是另一個問題。搜索行為和排序算法在語言和地區之間有所不同。

  3. 錯誤訊息也需要本地化，而不僅僅是翻譯。最好把錯誤代碼映射成本地化信息，而不是翻譯整個字串。

  4. 對於翻譯缺乏版本控制可能是災難性的，尤其是當商業需要經常變化的時候。

  5. 忽略訪問性翻譯可能會對使用者體驗有害，尤其是對於視覺障礙的個體。

此外，像Google Translate這樣的機器翻譯是非常不被鼓勵的。為了實現更成功的本地化，與能夠隨時識別潛在問題的本地團隊合作。

對於本地化有任何問題嗎？隨時提問。:)

  • 3 min read

On Imperfection

Is it difficult to create a book? The answer is debatable. Becoming a best-selling author is challenging if that's your sole aim. The process of writing, practicing, editing, and polishing takes a long time. The harsh truth is, if you're an unknown, few people will read what you've written. However, writing a book becomes simple if you commit to writing 50 words per day or one article per week. If you write consistently for a year, you'll have enough material to compile into a book, or perhaps a series of compilations.

Is it hard to give a speech? The answer is both yes and no. Speaking in front of an audience can be intimidating, especially if you aim to deliver a flawless performance that wows everyone. However, speaking on a topic for just two minutes is far from impossible. Anyone, regardless of their voice, body language, or rhetorical skills, can manage it. If the audience grasps your main point, that's already a success. There's no need to overthink it or let your fear of public speaking overwhelm you.

Is it challenging to maintain a healthy lifestyle? At first glance, it seems that committing to daily gym visits, getting out of a comfortable bed, and exerting the sweat and effort required for exercise can be quite demanding. However, running for 20 minutes or doing a few push-ups every day is certainly doable. Taking that first baby step can inspire you to continue and develop a positive habit.

Is dating difficult? No one said it would be easy, but you might be surprised by how challenging it can be. You might feel confident around your friends but freeze up in the presence of an attractive woman. While she's not a threat to you, the fear of embarrassing yourself may hold you back. There could also be other complications like her having a boyfriend or not being interested in men. As a result, she might not be captivated by your awkwardness. However, that's not the crucial point. What matters is enjoying your time and having a meaningful conversation.

While the list of activities could go on, there's a common thread: I set high standards for myself. I obsess over details and am preoccupied with outcomes, public opinion, and self-awareness. While this mindset might propel me to aim high, it also leads me to procrastinate. I didn't start writing until I felt sure of my ideas. I would decline speaking opportunities if I felt unprepared. I'd skip the gym if I could find enough excuses, and I'd hesitate to talk to strangers if I felt the need to impress them. My fear often inhibits me from taking the first step, leading to inaction. Mere thought, without action, leads nowhere.

Taking action, however, encourages further thought and more action. I've realized that things are usually not as bad as I had initially imagined. I've come to accept that my articles may not garner many likes, my speeches may not win international awards, I may not achieve a six-pack, and my partner may not be a supermodel. And that's okay. The outcome is beyond our control and depends on a mix of luck and statistics.

What truly matters is learning to love the process: finding therapy in focused writing, valuing the communication of a message in speaking, feeling energized through exercise, and simply having fun while socializing. Embracing the imperfections in your life can help you overcome imposter syndrome or the feeling of being a fraud who fears making mistakes. Even Albert Einstein, a bona fide genius, suffered from imposter syndrome. Why should ordinary people doubt their achievements?

So, what does it mean to be successful? Success is not defined by the outcome, but by progress: better writing, more practice in speaking, improved health, and enhanced social skills. Every small step toward continuous improvement is a success. It's something both you and I can achieve.

  • in podcast
  • 3 min read

On Imperfection

Welcome to Continuous Improvement, the podcast that explores the journey towards personal growth and success. I'm your host, Victor, and today we'll dive deep into the concept of continuous improvement. How can we overcome our fears and take action towards our goals? Let's find out!

Hello, my wonderful listeners. Today, I want to address something that many of us may struggle with at times: the fear of starting something new, the fear of failure, and the fear of not meeting our own high standards. It could be writing a book, giving a speech, maintaining a healthy lifestyle, or even the challenges of dating.

Let's start with writing a book. It's no secret that writing a book can be a daunting task. The process of writing, practicing, editing, and polishing takes time and dedication. But here's the secret to making it simpler: commit to writing just 50 words per day or one article per week. By consistently writing, you'll accumulate enough material over time, which can be compiled into a book or a series of compilations.

Now, let's talk about giving a speech. Speaking in front of an audience can be intimidating, especially if we aim for perfection. However, speaking on a topic for just a couple of minutes is far from impossible. The key is not to overthink it or let the fear of public speaking overwhelm us. As long as the audience grasps our main point, we've already succeeded. So, don't let the fear hold you back!

Maintaining a healthy lifestyle may seem challenging at first glance. Committing to daily gym visits or pushing yourself to exercise can be demanding. But here's the catch: running for just 20 minutes or doing a few push-ups every day is definitely doable. Taking that first baby step can inspire you to continue and develop a positive habit.

And let's not forget about dating. It can be quite a challenge, filled with insecurities and uncertainties. But remember, it's not about impressing others or meeting certain expectations. It's about enjoying your time and having a meaningful conversation. Let go of that fear of embarrassment and embrace the opportunity to connect with someone.

Now, let's talk about something that often holds us back: setting high standards for ourselves. While having high standards can push us to aim high, it also leads to procrastination and self-doubt. We hesitate to take action until we feel fully prepared, sometimes missing out on valuable opportunities.

But here's the truth we should embrace: things are usually not as bad as we initially imagine. Our articles may not gain countless likes, our speeches might not win awards, and our partners may not fit the mold of societal expectations. And that's perfectly fine. The outcome is beyond our control. What truly matters is learning to love the process, finding therapy in focused writing, valuing the communication of a message in speaking, feeling energized through exercise, and simply having fun while socializing.

Embracing imperfections and overcoming imposter syndrome allows us to appreciate our progress. Success is not defined by the outcome, but by continuous improvement, by taking those small steps towards growth. And that is something that both you and I can achieve.

Well, my friends, that's all for today's episode. I hope you found inspiration and encouragement in our discussion on continuous improvement. Remember, it's not about achieving perfection, but about embracing the journey towards growth.

Thank you for tuning in to Continuous Improvement. I'm Victor, your host, reminding you to take the first step and keep striving for progress. Until next time!

  • in zh
  • 1 min read

關於不完美

寫一本書難嗎？答案是有爭議的。如果你的唯一目標是成為暢銷書作家，那肯定是充滿挑戰的。寫作、練習、編輯和潤飾的過程需要很長時間。而令人不安的是，如果你是新手，很少有人會去閱讀你寫的東西。然而，如果你承諾每天寫50個字或每周寫一篇文章，寫作就變得容易了。如果你一年內持續寫作，你就有足夠的素材可以編成一本書，或者是一系列的合集。

演講難嗎？答案既是對的也是錯的。在觀眾面前演講可能會讓人感到恐慌，尤其是當你希望能完美無缺的演出來讓所有人驚訝。然而，只需講一個主題兩分鐘並不困難。任何人，不論他們的聲音、身體語言或說話技巧如何，都能辦得到。如果觀眾能抓到你的主要觀點，那就已經是一次成功的演講了。沒有必要深究，或讓你對公開演講的恐懼壓倒你。

維持健康的生活方式困難嗎？一開始看，每天都需要去健身房，早起離開舒適的床鋪，付出運動所需的汗水與努力，感覺似乎相當困難。但是，每天跑步二十分鐘或是每天做幾下俯臥撐是完全實行得到的。一旦迈出第一步，就有可能激發你繼續前進，發展一種積極的習慣。

交往難嗎？沒有人說過這會很容易，但你可能會對其困難程度感到驚訝。在朋友面前，你可能表現得信心滿滿，但在一個美女面前，你可能會變得膽小如鼠。儘管她對你來說並不構成威脅，但是對於尷尬的恐懼可能會阻止你的行動。還有其他的困難，比如她可能已經有男朋友，或者她對男性沒有興趣。結果，她可能不會被你的尷尬所吸引。但是，這都不是關鍵。最重要的是享受你的時間，並進行有意義的對話。

雖然這些活動的清單可以不斷延伸，但其中有一個共同點：我為自己設定了高標。我沉迷於細節，並對成果、公眾輿論和自我意識持續關注。這種心態可能使我抱負高遠，但也導致我耽誤時間。我在對自己的想法有了確定性之前並未開始寫作。如果我感到準備不足，我會拒絕演講的機會。如果我找到越多的藉口，我就會越容易取消健身的安排。如果我覺得需要給他人留下好印象，我就會對與陌生人搭訕感到猶豫不決。我的恐懼經常阻止我邁出第一步，導致我無法行動。單單思考而不去行動，只會讓我們白白浪費時間。

然而，行動起來后，會鼓舞人們進一步思考並促使他們持續行動。我意識到事情往往並不像我起初想象的那麼糟糕。我已經接受了我的文章可能不會得到太多的點讚，我的演講可能不會贏得國際大獎，我可能達不到六塊肌的目標，我的伴侶可能不會是超模。而這一切都沒關係。結果是我們不能控制的，取決於運氣和各種機會的結合。

真正重要的是學會熱愛過程：寫作中尋找治療效果，講話中的信息傳遞，運動帶來的活力，還有社交中的樂趣。接受生活中的不完美可以幫助你克服冒名者症候群，或者是害怕犯錯，覺得自己是個騙子的感覺。即使是像阿爾伯特·愛因斯坦這樣的天才，也曾深受冒名者症候群的困擾。那麼我們這些普通人有什麼理由去質疑自己的成就呢？

那麼，什麼是成功？成功並不是由結果來定義，而是由進步來定義：寫作能力的提高，講話練習的增加，健康狀況的改善，和社交技巧的提高。每一個朝著持續進步的小步驟都是成功。這是你我都能達到的。

  • 3 min read

Continuous Improvement

Thank you for taking the time to read my book and journey through my life experiences with me. You likely have your own set of challenges and obstacles. That’s why you sought out my book—to understand how I’ve managed to navigate through mine.

I failed in my first twelve romantic relationships. It's not that I wasn't appealing; in fact, I changed my appearance after the first six failures, opting for a better haircut and more suitable attire. Nevertheless, I continued to struggle. I hoped each new relationship would be an improvement over the last, but marriage remained elusive. I share my experiences to help you avoid making the same mistakes.

So why do relationships fail? It might be because your qualities aren't as compelling as those of other potential partners, making you less attractive or financially desirable. Your partner might simply prefer someone else; after all, there are plenty of fish in the sea.

What can you do about it? My book advises you to focus on two words: continuous improvement. Rather than indulging in jealousy or self-pity, steer clear of negativity.

To improve, engage with life fully, deepen your relationships, and showcase your best qualities. Work on advancing your career, expanding your social circle, and enhancing your physical well-being. This change will not only shift how people perceive you, but also improve your odds if a potential partner is choosing between you and someone else. You’ll be seen as a person who values self-improvement and long-term growth.

You see, current circumstances are not permanent indicators of future success. I may be facing challenges now, but that doesn’t define my future. Before achieving your goals, you must first demonstrate your potential. Self-improvement is crucial; it allows your partner to recognize your latent talents and aspirations.

Your competition might not be as committed to personal growth. Even if they currently surpass you in some qualities, you can bridge that gap through persistent effort. Fashion sense is one example. If you and your girlfriend share a similar style, she’ll likely view you as compatible.

It's not the end of the world if your current relationship doesn't work out. Continuous improvement will expand your opportunities. The key is to avoid pressuring your partner into making a decision about the relationship. No one likes to feel coerced; people prefer to make choices freely. Give your partner the space to decide whether they see a future with you.

Are you the kind of man who embraces this philosophy? That's why you picked up this book—to be inspired to become a better person. Don't worry about making a single mistake. What’s essential is maintaining a positive atmosphere in your relationship. Inject humor, engage in healthy debates, and set challenges just as you would in public speaking. Know when to compliment and flatter; the right words at the right time can elevate the relationship.

Furthermore, it's important to have a sense of purpose in life that extends beyond your own benefit. If you appear selfish, no woman would want to envision a future with you. Understand your responsibilities within the larger society. Strive to be someone who can contribute positively to the world. That's an attractive quality.

In summary, remember the principle of freedom. Let your partner choose you without feeling pressured. Focus less on your competition and more on exuding a positive energy.

I hope you find my book helpful. If so, please recommend it to others who might benefit. Not only will this improve your romantic relationships, but it will also make you a more valuable colleague and friend.

  • in podcast
  • 3 min read

Continuous Improvement

Welcome to Continuous Improvement, the podcast where we explore strategies and insights to help you navigate the challenges and obstacles in life. I'm your host, Victor, and in today's episode, we'll be diving into the topic of relationships and continuous improvement.

Relationships can be complicated, and we've all faced our fair share of failures and disappointments. In fact, I personally struggled through twelve failed romantic relationships before finding success. But it's not about dwelling on those failures; it's about learning from them and continuously improving ourselves.

In my book, I share my experiences and provide guidance on how to avoid making the same mistakes I did. One important concept that I emphasize is continuous improvement. Rather than succumbing to negativity and self-pity, we must embrace personal growth and strive to be the best versions of ourselves.

So why do relationships fail? Well, there could be various factors at play. It could be that our qualities aren't as compelling as those of other potential partners. Or perhaps our partner simply prefers someone else. But what can we do about it?

The answer lies in continuous improvement. We must engage fully with life, deepen our relationships, and showcase our best qualities. By advancing our careers, expanding our social circles, and enhancing our physical well-being, we not only change how others perceive us but also increase our odds of finding a lasting and fulfilling relationship.

Remember, current circumstances do not define our future success. We must demonstrate our potential and constantly work on ourselves. While it may seem daunting, this continuous improvement allows our partners to see our latent talents and aspirations.

The competition out there may appear more polished, but we can bridge that gap through persistent effort. Take fashion sense, for example. If you and your partner share a similar style, it creates a sense of compatibility. It's about finding those areas where you can shine and showcase your uniqueness.

Now, if your current relationship doesn't work out, it's not the end of the world. Continuous improvement expands your opportunities. You must resist the urge to pressure your partner into making a decision. Give them the space to determine whether they see a future with you.

Embracing continuous improvement means maintaining a positive atmosphere in your relationship. Inject humor, engage in healthy debates, and set challenges. Compliment and flatter your partner when appropriate. These actions can elevate the relationship and create a strong foundation built on trust and respect.

But remember, it's not just about focusing on ourselves and our relationships. Having a sense of purpose that goes beyond personal benefit is essential. This demonstrates that we are not only committed to our own growth but also to making a positive impact in the world around us. And that's an attractive quality.

In summary, let your partner choose you freely without feeling pressured. Shift your focus from competing with others to exuding positive energy. Continuous improvement is a lifelong journey, and it applies not only to our romantic relationships but also to every aspect of our lives.

I hope you found today's episode insightful and inspiring. Remember, it's okay to make mistakes along the way. What truly matters is maintaining a positive atmosphere and embracing continuous improvement.

Thank you for joining me on this episode of Continuous Improvement. If you found value in today's discussion, I encourage you to recommend this podcast to others who may benefit from it. Together, let's strive to become better versions of ourselves and make a positive difference in the world.