At the A1 level, you can think of 企画書 (kikakusho) as a 'project paper.' It is a special piece of paper where you write your ideas for a new plan. In a Japanese company, everyone uses these papers. Even if you are just starting to learn Japanese, you might hear this word in a classroom when a teacher asks for a 'plan' for a group activity. It is a noun. You can say 'kikakusho o kakimasu' (I write a proposal). It is made of three kanji: 企 (plan), 画 (picture/drawing), and 書 (write/book). Together they mean 'a document for a drawn-out plan.' It is very important for work. If you want to make a new game, a new food, or a new event, you need a 企画書. It usually has the name of the project and the price. You should remember it as 'Business Proposal Paper.'
At the A2 level, 企画書 (kikakusho) is understood as a formal 'proposal document.' You should know that it is used with the particle 'o' and verbs like 'tsukuru' (make) or 'dasu' (submit). For example, 'Kinou, kikakusho o dashimashita' (I submitted the proposal yesterday). This word is essential for anyone interested in Japanese business culture. It's more formal than just an 'idea' (idea/an). When you use this word, people think you are talking about a professional document with sections like 'purpose,' 'target,' and 'cost.' You might see this word on the cover of a folder or in the subject of an email. It is pronounced 'ki-kaku-sho.' Remember that the 'ki' and 'ka' are short sounds. It is a very common word in office settings and is one of the first 'business' words students learn.
At the B1 level, you should understand 企画書 (kikakusho) as a 'comprehensive project proposal.' At this stage, you should be able to distinguish it from similar documents like 提案書 (teiansho - proposal/suggestion) and 報告書 (houkokusho - report). A 企画書 is specifically for the 'planning' phase of a project. You will often hear it used with more advanced verbs like 'sakusei suru' (to create/draft) or 'matomeru' (to compile). For example, 'Puresen no tame ni kikakusho o matometeimasu' (I am compiling the proposal for the presentation). You should also be aware of the phrase 'kikakusho ga tooru' (the proposal passes/gets approved), which is a key goal in a Japanese company. This level involves understanding that a 企画書 needs to be persuasive and logically structured to be successful in a Japanese professional environment.
At the B2 level, 企画書 (kikakusho) represents a strategic document that requires careful 'nemawashi' (prior consultation) before it is officially submitted. You should be able to discuss the contents of a 企画書 using specific business terminology, such as 趣旨 (shushi - purpose), 予算 (yosan - budget), and 期待される効果 (kitai sareru kouka - expected effects). You might encounter sentences like 'Kono kikakusho wa setsuneryoku ni kaketeiru' (This proposal lacks persuasive power). At this level, you understand that the 企画書 is a reflection of the writer's analytical skills and their ability to align a project with the company's goals. You should also be familiar with related terms like 企画立案 (kikaku ritsuan - project planning and drafting) and how the 企画書 fits into the broader corporate decision-making process, including the 'ringi' (consensus-based decision making) system.
At the C1 level, 企画書 (kikakusho) is treated as a sophisticated tool for organizational change and strategic initiative. You should be able to critique a 企画書 for its logical consistency, market alignment, and risk assessment. The term often appears in discussions about corporate strategy, where a 企画書 might be the catalyst for a major pivot or a new business line. You should be comfortable using the word in high-level keigo (honorific Japanese) contexts, such as 'Kikakusho o go-ran itadakereba saiwai desu' (I would be honored if you would look at the proposal). You also understand the cultural nuances behind the document—how it serves as a record of consensus and how its structure might vary between traditional 'Nikkei' companies and modern 'Gaishikei' (foreign) firms. Mastery at this level involves being able to lead a team in the collaborative creation of a high-stakes 企画書.
At the C2 level, you possess a native-like intuition for the strategic and political weight a 企画書 (kikakusho) carries within a Japanese hierarchy. You understand it not just as a document, but as a symbolic gesture of professional commitment and vision. You can navigate the complexities of drafting a 企画書 that satisfies multiple stakeholders with competing interests, using subtle linguistic cues to build support. You are aware of historical and contemporary shifts in how these documents are produced, from the traditional 'Ringisho' style to modern, data-driven pitch decks. In professional discourse, you can use the term metaphorically to discuss the 'blueprint' of complex socio-economic policies or philosophical frameworks. Your command of the language allows you to facilitate the entire lifecycle of a 企画書, from the initial 'kousou' (vision) to the final 'shounin' (approval) and subsequent implementation, with absolute precision and cultural sensitivity.

企画書 in 30 Sekunden

  • A 企画書 (kikakusho) is a formal Japanese business document used to propose and plan new projects, products, or events within an organization.
  • It typically contains sections for the project's purpose, target, budget, and timeline, and is essential for the consensus-building decision-making process.
  • Commonly used verbs include 'sakusei suru' (to create), 'teishutsu suru' (to submit), and 'tooru' (to be approved or pass).
  • While similar to a 'teiansho' (proposal), a 'kikakusho' is usually more focused on the internal execution and detailed blueprint of the plan.

The Japanese word 企画書 (きかくしょ - kikakusho) is a fundamental term in the Japanese professional landscape, translating primarily to 'proposal document' or 'project plan.' In the context of Japanese business culture, which emphasizes meticulous preparation and consensus-building (known as nemawashi), the 企画書 is the formal manifestation of an idea. It is not merely a suggestion; it is a structured document designed to persuade stakeholders, outline logistical requirements, and secure budgetary approval.

Core Concept
A formal document detailing a new project, product, or event, intended to gain approval from superiors or clients.

You will encounter this word daily if you work in a Japanese office, particularly in departments like marketing, sales, or product development. When a team lead says, "企画書をまとめておいて" (Summarize the proposal), they are asking for a comprehensive breakdown of the 'what,' 'why,' 'how,' and 'how much.' Unlike a simple memo, a 企画書 often follows a specific internal template that includes market analysis, target audience, schedule, and projected ROI.

来週の会議までに、新商品の企画書を完成させる必要があります。
(We need to complete the proposal document for the new product by next week's meeting.)

The nuances of 企画書 distinguish it from other business documents. While a 提案書 (teiansho) is a general 'proposal' or 'suggestion' often sent to external clients, a 企画書 is frequently internal-facing or highly detailed. It bridges the gap between a raw idea and an actionable project. In Japanese media, especially 'workplace' dramas, the struggle to get a 企画書 approved by a stubborn boss is a common trope representing professional growth and persistence.

Usage Context
Used in project management, advertising, event planning, and any scenario requiring formal authorization for a new initiative.

Furthermore, the term is often paired with verbs like 作成する (sakusei suru - to create), 提出する (teishutsu suru - to submit), and 通る (tooru - to pass/be approved). If your 企画書 'passes' (企画書が通る), it means you have the green light to proceed with the project. This is a moment of great celebration for Japanese salarymen and office ladies alike. The word embodies the transition from thought to action within a corporate hierarchy.

部長に企画書を提出しましたが、修正を求められました。
(I submitted the proposal to the department manager, but I was asked to make revisions.)

Using 企画書 correctly requires understanding its role as a noun and the verbs that typically accompany it. In a professional setting, the focus is often on the lifecycle of the document: drafting, submitting, reviewing, and approving. Because it is a formal document, the surrounding language is usually polite (Desu/Masu) or humble/honorific (Keigo) depending on the hierarchy.

Common Verb Pairings
作成する (to create), 提出する (to submit), 修正する (to revise), 承認する (to approve), 却下する (to reject).

When you are the one writing the document, you use verbs related to production. For example, "企画書を練る" (kikakusho o neru) means to 'knead' or 'work out' the proposal, suggesting a deep level of thought and refinement. This is a more nuanced way to describe the creative process than just 'writing.'

一晩中かかって、イベントの企画書を練り上げた。
(I spent all night working out the event proposal to completion.)

In a passive sense, or when referring to the status of the document, you might hear "企画書が通る" (the proposal passed) or "企画書がボツになる" (the proposal was scrapped/rejected). 'Botsu' is a common business slang term for something being tossed in the trash. Using these expressions correctly shows a high level of fluency in corporate Japanese culture.

When discussing the content of the proposal, you might use the particle 'の' to describe the subject. For instance, "広告キャンペーンの企画書" (Proposal for an advertising campaign). This structure is very common in email subject lines and folder titles in a digital workspace. It is also helpful to know that a 企画書 can be digital (PDF, PowerPoint) or physical, though digital is now standard.

この企画書、もう少し具体的に書けませんか?
(Could you write this proposal a bit more specifically?)

Sentence Structure Tip
[Project Name] + の + 企画書 + [Object Particle を] + [Verb]. Example: YouTube動画の企画書を作る。

The word 企画書 is ubiquitous in any environment where ideas are monetized or managed. If you are a fan of Japanese anime or manga, you'll often see creators presenting a 企画書 to publishers or producers. In the world of 'Shonen Jump' or similar magazines, the 企画書 is the first step for a manga artist to get a serialization. It contains character designs, plot summaries, and the 'hook' of the story.

アニメ制作の第一歩は、魅力的な企画書を作ることです。
(The first step in anime production is creating an appealing proposal document.)

In a modern Japanese startup, you might hear the word used in a more fast-paced, digital context. Entrepreneurs talk about their 'pitch deck' as a 企画書 when speaking to traditional Japanese investors. Here, the word carries the weight of professional reliability. If you go to a coworking space in Shibuya or Minato, you'll likely see people staring at screens with "企画書_最終版_v3" (Proposal_Final_v3) open in PowerPoint or Google Slides.

Television programs also use this term behind the scenes. TV producers (P) and directors (D) are constantly 'passing' 企画書 for new variety shows or drama specials. Sometimes, the term is used in the shows themselves to depict a character's hard work. A scene where a character is seen sleeping at their desk surrounded by papers usually implies they were struggling with a 企画書 until dawn.

Places of Usage
Offices, Universities, Creative Studios, Government Agencies, Pitch Competitions.

In the government or public sector, a 企画書 might be more rigid and formal, often referred to as a 'project plan' for urban development or public policy. In this context, it is a document of public record. Whether it's a small internal team or a massive government project, the 企画書 remains the universal 'blueprint' for the future in Japan.

市役所に新しい公園の企画書を提出した。
(I submitted a proposal for a new park to the city hall.)

One of the most frequent mistakes learners make is confusing 企画書 (kikakusho) with 提案書 (teiansho). While both involve proposing something, a 提案書 is often broader and focuses on 'suggesting' a solution to a problem, while a 企画書 is a specific 'plan' for a project that the writer intends to execute. If you use 企画書 when you just mean a vague suggestion, it might sound like you have a full project plan ready when you don't.

Mistake 1: Confusion with Reports
Confusing 企画書 with 報告書 (houkokusho). A 報告書 is a report on something that has already happened, whereas a 企画書 is about something that will happen.

Another mistake is the pronunciation. The first kanji 企 (ki) is often confused with 気 (ki) or 木 (ki). In 企画, the 'ki' is short. The second kanji 画 (kaku) can sometimes be misread as 'ga' (as in eiga - movie), but in this compound, it is strictly 'kaku.' Ensure you say 'ki-kaku-sho' clearly to avoid sounding like you're talking about a 'tree document' (木書 - which isn't a word, but might confuse listeners).

❌ 昨日のイベントの企画書を書きました。
✅ 昨日のイベントの報告書を書きました。
(Use 'report' for things in the past.)

Learners also struggle with the level of formality. Since a 企画書 is a formal document, you should rarely use informal verbs like 'kaku' (to write) when talking to a boss. Use 'sakusei suru' (to create/draft) or 'matomeru' (to compile/summarize). Using 'kaku' makes it sound like a casual school essay rather than a professional business plan.

Mistake 2: Particle Usage
Using 'ni' instead of 'o' for the object. It is always '企画書を出す' (submit the proposal), not '企画書に出す'.

To truly master Japanese business vocabulary, you need to know where 企画書 sits in relation to its synonyms. The most common alternative is 提案書 (てあんしょ - teiansho). The difference is subtle but important: 提案書 focuses on the 'proposal' of an idea or solution to a client, while 企画書 is a 'project plan' detailing the execution. Often, a 提案書 comes first to see if the client is interested, and once they say yes, a 企画書 is written to outline the actual project.

Comparison: 企画書 vs 提案書
企画書: Detailed plan, focus on execution, internal or project-specific.
提案書: Suggestion, focus on benefits/solutions, often external/sales-oriented.

Another related word is 案 (あん - an). This simply means 'plan,' 'idea,' or 'draft.' It is much less formal than 企画書. You might say "私の案" (my idea) in a casual brainstorming session. Once that 'an' is written down into a formal document, it becomes a 企画書. There is also 計画書 (けいかくしょ - keikakusho), which is a 'schedule' or 'plan document.' This is more about the timeline and logistics (the 'when') than the creative idea (the 'what').

企画書は「何を」するか、計画書は「いつ、どうやって」するかを詳しく書いたものです。
(A kikakusho is about 'what' to do; a keikakusho is about 'when and how' to do it in detail.)

For very high-level documents, you might hear 構想 (こうそう - kousou), which means 'vision' or 'grand plan.' This is used for massive projects like city planning or a series of novels. Finally, 設計図 (せっけいず - sekkeizu) refers specifically to 'blueprints' or 'design drawings' in engineering or architecture. While a 企画書 might include a 設計図, they are distinct entities.

Summary of Alternatives
案 (Draft/Idea), 提案書 (Proposal), 計画書 (Plan/Schedule), 仕様書 (Specs), 構想 (Vision).

Wusstest du?

The kanji '企' (ki) originally depicted a person standing on tiptoe to look into the distance, symbolizing looking ahead or planning for the future.

Aussprachehilfe

UK ki.ka.kɯ.ɕo
US ki.ka.kɯ.ʃoʊ
Japanese has pitch accent rather than stress. 企画書 typically has a 'Heiban' (Flat) or 'Atamadaka' (Initial high) pattern depending on the dialect, but in standard Tokyo Japanese, it is generally flat after the first syllable.
Reimt sich auf
読書 (dokusho) 辞書 (jisho) 秘書 (hisho) 報告書 (houkokusho) 履歴書 (rirekisho) 説明書 (setsumeisho) 教科書 (kyoukasho) 専門書 (senmonsho)
Häufige Fehler
  • Pronouncing 'kikaku' as 'kikāku' (long 'a').
  • Confusing 'sho' with 'shou' (long 'o').
  • Putting stress on the wrong syllable like 'ki-KA-ku-sho'.
  • Misreading 'kaku' as 'ga'.
  • Mixing up 'kikaku' with 'kikaku' (standardization - different kanji).

Beispiele nach Niveau

1

これは企画書です。

This is a proposal document.

Basic 'A wa B desu' structure.

2

企画書を書きます。

I will write a proposal.

Object particle 'o' used with the verb 'kakimasu'.

3

新しい企画書です。

It is a new proposal.

Adjective 'atarashii' modifying the noun.

4

企画書を読みます。

I read the proposal.

Verb 'yomimasu' (to read).

5

企画書はどこですか?

Where is the proposal?

Question word 'doko' (where).

6

この企画書はいいですね。

This proposal is good, isn't it?

Demonstrative 'kono' and particle 'ne'.

7

企画書を見せてください。

Please show me the proposal.

Request form '~te kudasai'.

8

企画書が三枚あります。

There are three sheets of proposals.

Counter for thin flat objects 'mai'.

1

明日までに企画書を作ります。

I will make the proposal by tomorrow.

Time limit marker 'made ni'.

2

企画書をカバンに入れました。

I put the proposal in my bag.

Directional particle 'ni' with 'iremasu'.

3

もっと短い企画書が必要です。

A shorter proposal is necessary.

Comparative 'motto' and 'hitsuyou' (necessary).

4

企画書をメールで送りました。

I sent the proposal by email.

Means/method particle 'de'.

5

会議で企画書を配ります。

I will distribute the proposals at the meeting.

Location of action particle 'de'.

6

この企画書はわかりやすいです。

This proposal is easy to understand.

Compound verb ending '~yasui'.

7

企画書の名前を変えました。

I changed the name of the proposal.

Possessive particle 'no'.

8

一緒に企画書をチェックしましょう。

Let's check the proposal together.

Volitional form '~mashou'.

1

企画書の内容を修正してください。

Please revise the content of the proposal.

Formal request using 'shuusei' (revision).

2

やっと企画書が通りました!

The proposal finally passed!

Adverb 'yatto' (finally) and intransitive verb 'tooru'.

3

企画書を提出する前に、もう一度確認します。

I will check one more time before submitting the proposal.

Clause connector 'mae ni' (before).

4

彼は企画書をまとめるのが上手です。

He is good at compiling proposals.

Nominalizer 'no' and 'jouzu' (skillful).

5

企画書に予算を書き忘れてしまいました。

I accidentally forgot to write the budget in the proposal.

Regret/accident form '~te shimau'.

6

どんな企画書なら、部長は納得するでしょうか?

What kind of proposal would convince the department manager?

Conditional 'nara' and 'darou ka' (wondering).

7

企画書の締め切りは来週の月曜日です。

The deadline for the proposal is next Monday.

Noun 'shimekiri' (deadline).

8

イベントの企画書を練り直す必要があります。

We need to rework the event proposal.

Verb 'nerinaosu' (to rework/knead again).

1

企画書の趣旨が不明確だと指摘されました。

It was pointed out that the purpose of the proposal is unclear.

Passive voice 'shiteki sareta'.

2

この企画書には、具体的なデータが不足しています。

This proposal lacks specific data.

Verb 'fusoku shiteiru' (to be lacking).

3

企画書をブラッシュアップして、再提出します。

I will brush up the proposal and resubmit it.

Loan word 'burasshu appu' (brush up).

4

競合他社に勝つための企画書を立案中です。

We are currently drafting a proposal to beat our competitors.

Purpose marker 'tame no' and 'chuu' (currently doing).

5

企画書が却下された理由は、コストが高すぎたからです。

The reason the proposal was rejected was that the cost was too high.

Passive verb 'kyakka sareta' and 'kara desu' (reason).

6

上司と相談しながら、企画書を完成させました。

I completed the proposal while consulting with my boss.

Simultaneous action '~nagara'.

7

この企画書は、市場のニーズを的確に捉えています。

This proposal accurately captures the needs of the market.

Adverb 'tekikaku ni' (accurately).

8

企画書の作成に、丸三日かかりました。

It took three whole days to create the proposal.

Duration 'maru mikka' (three full days).

1

企画書の妥当性を検証するために、追加の調査が必要です。

Additional research is needed to verify the validity of the proposal.

Formal noun 'datousei' (validity) and 'kenshou' (verification).

2

その企画書は、社の長期的なビジョンと合致しています。

That proposal aligns with the company's long-term vision.

Formal verb 'gacchi suru' (to align/coincide).

3

斬新な企画書を提示することで、役員たちを驚かせた。

He surprised the executives by presenting a groundbreaking proposal.

Causative verb 'odorakaseda' (made them surprised).

4

企画書を精査した結果、いくつかのリスクが浮き彫りになった。

As a result of scrutinizing the proposal, several risks have come to light.

Formal verb 'seisa' (scrutiny) and idiom 'ukibori ni naru'.

5

この企画書は、単なるアイデアの羅列に過ぎない。

This proposal is nothing more than a list of ideas.

Grammar pattern '~ni suginai' (nothing more than).

6

企画書の採択は、次回の取締役会で決定されます。

The adoption of the proposal will be decided at the next board meeting.

Formal noun 'saitaku' (adoption/selection).

7

彼は企画書を通じて、自身の熱意をアピールした。

He promoted his enthusiasm through the proposal.

Marker 'tsuujite' (through/via).

8

説得力のある企画書を作成するには、論理的な思考が不可欠だ。

Logical thinking is indispensable for creating a persuasive proposal.

Formal adjective 'fukaketsu' (indispensable).

1

本企画書は、多角的な視点から事業の持続可能性を論じています。

This proposal discusses the sustainability of the business from multifaceted perspectives.

Formal prefix 'hon' (this) and 'tagakuteki' (multifaceted).

2

企画書の行間に込められた意図を読み取ることが肝要である。

It is essential to read the intentions hidden between the lines of the proposal.

Idiom 'gyoukan o yomu' and formal 'kanyou' (essential).

3

その企画書が承認されるや否や、プロジェクトチームが結成された。

As soon as the proposal was approved, a project team was formed.

Grammar pattern '~ya ina ya' (as soon as).

4

企画書の不備を突かれ、説明に窮する場面もあった。

There were moments where I struggled to explain after the flaws in the proposal were pointed out.

Passive 'tsukare' and 'kyuu suru' (to be at a loss).

5

この企画書は、既存の概念を覆す可能性を秘めている。

This proposal holds the potential to overturn existing concepts.

Verb 'kutsugaesu' (to overturn) and 'himeru' (to hide/hold).

6

企画書の文言一つ一つに、細心の注意を払わなければならない。

We must pay the closest attention to every single word in the proposal.

Expression 'saishin no chuui o harau'.

7

社運を賭けた大規模なプロジェクトの企画書が、ついに完成した。

The proposal for a massive project on which the company's fate rests has finally been completed.

Idiom 'shaun o kaketa' (betting the company's luck).

8

企画書における費用対効果の算出根拠を、厳密に再定義する。

We will strictly redefine the basis for calculating cost-effectiveness in the proposal.

Formal 'sanshutsu konkyo' (basis for calculation).

Häufige Kollokationen

企画書を作成する
企画書を提出する
企画書が通る
企画書を練る
企画書を修正する
企画書にまとめる
企画書を却下する
企画書の締め切り
企画書を検討する
企画書を持ち込む

Häufige Phrasen

企画書一式

— A complete set of proposal documents.

企画書一式を郵送します。

企画書作成中

— Currently in the process of creating a proposal.

今は企画書作成中です。

通る企画書

— A proposal that is likely to be approved (a 'winning' proposal).

通る企画書の書き方を教える。

企画書お断り

— No proposals accepted (often seen in solicitations).

営業の企画書はお断りしています。

企画書代行

— Proposal writing service/agency.

企画書代行サービスを利用する。

企画書テンプレート

— A template for a proposal document.

使いやすい企画書テンプレートを探す。

企画書の中身

— The content of the proposal.

企画書の中身が薄い。

企画書の趣旨

— The main point or purpose of the proposal.

企画書の趣旨を説明する。

企画書ボツ

— A rejected or scrapped proposal.

一生懸命書いた企画書がボツになった。

企画書が命

— The proposal is everything/crucial.

コンペでは企画書が命だ。

Redewendungen & Ausdrücke

"企画書を丸める"

— Metaphorically, to scrap or ignore a proposal (literally to roll up the paper).

部長はその企画書を丸めて投げ捨てた。

Informal
"企画書に魂を込める"

— To put one's heart and soul into a proposal.

魂を込めた企画書なら必ず通る。

Emotional
"企画書が一人歩きする"

— When a proposal starts being discussed or implemented without the author's control.

企画書が一人歩きして、内容が変わってしまった。

Business
"企画書を叩き台にする"

— To use a proposal as a springboard or a 'beating block' for further discussion.

まずはこの企画書を叩き台にしましょう。

Business
"企画書の山"

— A mountain of proposals (implying high competition or busy workload).

デスクに企画書の山ができている。

Neutral
"企画書を寝かせる"

— To let a proposal sit for a while before finalizing it (to get fresh eyes).

一晩企画書を寝かせてから見直す。

Creative
"企画書をひっくり返す"

— To completely overturn or reject a previously accepted proposal.

社長が突然企画書をひっくり返した。

Informal
"企画書に落とし込む"

— To translate ideas or concepts into the formal structure of a proposal.

議論した内容を企画書に落とし込む。

Business
"企画書の顔"

— The title or first page of the proposal (the 'face').

企画書の顔が地味だと読んでもらえない。

Business
"企画書を潰す"

— To intentionally sabotage or kill a proposal.

ライバルの企画書を潰すつもりだ。

Informal

Wortfamilie

Substantive

企画 (Planning)
企画者 (Planner)
企画力 (Planning ability)
企画案 (Proposal draft)

Verben

企画する (To plan/design)

Adjektive

企画的な (Strategic/Planning-oriented)

Verwandt

計画 (Plan)
立案 (Drafting)
提案 (Proposal)
承認 (Approval)
実施 (Implementation)

Einprägen

Eselsbrücke

Imagine a **KEY** (Ki) hitting a **CACTUS** (Kaku) while you are trying to write on a **SHOW** (Sho) poster. Key-Kaku-Sho.

Visuelle Assoziation

Picture a sleek, white folder with a bright '💡' lightbulb icon on it, sitting on a boardroom table.

Word Web

Office Paper Idea Money Boss Meeting Success Draft

Herausforderung

Try to say 'Kikakusho o dashimashita' (I submitted the proposal) five times fast without tripping over the 'k' sounds.

Wortherkunft

Composed of 企画 (kikaku) and 書 (sho). 'Kikaku' refers to planning or undertaking a project. 'Sho' refers to a document or book.

Ursprüngliche Bedeutung: A document for undertaking a project.

Sino-Japanese (Kango).

Kultureller Kontext

Be careful not to sound too demanding when asking someone for a 企画書; use 'onegai shimasu' to maintain politeness.

In English business culture, a 'pitch' or 'proposal' might be more oral-focused or use a 'deck' (PowerPoint), whereas the Japanese 企画書 is traditionally a more text-heavy, formal document.

Used frequently in the anime 'Shirobako' which details the anime production process. Common theme in the drama 'Hanzawa Naoki' regarding bank loans and business plans. Key plot point in 'Bakuman' regarding manga serialization.
War das hilfreich?
Noch keine Kommentare. Sei der Erste, der seine Gedanken teilt!