Denys Lytovchenko, 33

Outcome. The "30 min" pilot introduces a standard for recording reasons for delays.

World engine: Preparation of the technical package and correspondence - own operational resources, without expenses.

Place: Delivery office · Pivdenno-Zakhidnyi

Thoughts

I have already launched the pilot and invested in operational preparations, but now I need the next step: to quickly "land" the metrics and eliminate conflicts with the traffic flow. Bohdan confirmed the locations, but Pavlo missed the meeting again - so I won't wait. I will create a short technical coordination package: arrival/parking windows, control of delay reasons, reporting format for pickup nodes. This way, I will reduce the risks of SLA breaches and provide arguments that can be shown to both the city and the bank/auditors, without any politics.

Options

1. Prepare and send a technical package to Pavlo Humeniuk without a meeting: time slots, routes, peak scenarios, window requirements. In parallel - a short plan for Bohdan with...
2. Arrange an urgent meeting with Bohdan Kravets (face-to-face) to synchronize operational rules at the two markets, to compensate for the lack of agreement with Pavlo...
3. Launch a third "pickup node" location without approval (experimentally) and only then legalize the rules - this will increase coverage faster, but the risk of...

Choice. I choose option 1: I need approval of windows and reasons for delays specifically for transport, not just for Kravets' operations. The package without a meeting provides speed and leaves a clear trail of actions.

Statement: «In the "30 minutes" pilot, I am implementing a standard for recording reasons for delays and agreed arrival/unloading windows - so that the speed is measurable and repeatable, not just an impression.»

Diary. Today, without waiting for a meeting, I took the next step for the pilot: I am preparing a technical package on time slots and the standard for recording reasons for delays and sending it to Pavlo Humeniuk with a deadline of 48 hours. In parallel, I am synchronizing Bohdan/Andrii Tkach: quality data on nodes and discipline at the locations are needed. My task is to ensure that the 30-minute SLA is maintained not only by the operational...

Outcome. The delivery service is launching a 6-week pilot with time corridors for couriers

World engine: Expenses of UAH 42,000 within own funds (UAH 357,000) for the delivery pilot.

Place: Tsentralnyi

Thoughts

I need the next step for my KPI of '30 min': Pavlo Humeniuk provided time windows for problem areas, but the meeting has not yet taken place. Currently, I have low influence in the city, so I need to quickly conduct a practical pilot: coordinate with delivery operators (and transport authorities) the pickup/entry mode into the center during peak hours. In parallel, I cannot get involved in the 'embankment' again — there is too much politics and audits there. Focus: traffic, entries, pickup points, SLA, and data collection. The best approach is to offer Bohdan specific locations/traffic rules and promise him a business-safe format, avoiding conflicts.

Options

1. Propose to Bohdan a pilot at 2 locations in the center with 'peak windows' and SLA fixation; in parallel, send Pavlo Humeniuk a technical request for time corridors for...
2. Build a city protocol 'SLA 30 min + traffic corridors' and submit it to the department/transport enterprise without personal coordination with Pavlo (quickly, and...
3. Instead of a pilot, a media move through a newspaper/blogger about transparent delivery rules during peak hours (may improve reputation, but won't add data).

Choice. Option 1. It provides both data and practical frameworks, directly based on Pavlo's remarks, and reduces tension with Bohdan through clear business rules.

Statement: «I am preparing a technical pilot '30 min during peak hours': we will fix the delivery SLA and courier traffic corridors in central locations so that speed does not depend on traffic chaos.»

Diary. After Pavlo Humeniuk's response, I decided not to wait for the meeting but to close the 'painful' hours through operational corridors in the pilot. Today I am launching a 6-week discipline: 2 pickup points, labels for reasons for delays, SLA 30 min control during peak windows 8–10 and 17–19. I spent UAH 42,000 on preparing the operational part. In parallel, I asked Pavlo to specify p...

World engine: Operational work within previously agreed funds, without new expenses.

Place: Delivery office · Pivdenno-Zakhidnyi

Thoughts

Bohdan signed the SLA+KPI and has already provided the funds, so my task is not to disrupt the release schedule of the issuance nodes and to make the analytics defensible in the city services without politics. The tension with Kravets is palpable, but the best move now is to standardize the process: unified KPI rules, control points, responsible parties, and a release calendar. Plus: I want to reduce traffic risk by involving the city transport enterprise through Pavlo Humeniuk, although relations are neutral. This should strengthen the arguments for a sustainable "30 min" pilot. Little money: need to act point-wise, without unnecessary expenses.

Options

1. Launch the technical "release timeline" for issuance nodes and connect analytics (tags, delay reason collection) with clear control dates; in parallel, write...
2. Hold a short meeting with Pavlo Humeniuk regarding entry/parking windows near the pilot locations and agree on minimal traffic rules for couriers/micro-transport;...
3. Try to strengthen the public side: offer the "Chronicle 2046" editorial office a neutral article about the technical KPIs of the "30 min" pilot to reduce media noise...

Choice. I choose option 2 + the basis of option 1. Without agreed city windows, traffic will eat the SLA, and a standardized timeline and responsibility with Bohdan will provide control over execution.

Diary. Today I set a course for execution control: I am breaking down the release of issuance nodes into clear control dates and adding a matrix of delay reasons, so that the SLA is measured unambiguously. The tension with Bohdan does not disappear, so it is important to speak the language of process and responsibility. In parallel, I am asking Pavlo Humeniuk to agree on practical windows near the pickup points - without this, "30 min" will remain...

Outcome. Delivery service launches technical data collection circuit for the pilot.

World engine: UAH 200,000 of own funds for pilot analytics, within available funds.

Place: Delivery office · Pivdenno-Zakhidnyi

Thoughts

I confirmed the 30-minute pilot idea, but now it's important not to lose momentum: there is money for analytics (UAH 200,000), there is Bohdan's consent for 6 weeks, only the operational start of integration of pickup points and fixing the SLA is missing, so that it can withstand both city inspection and skepticism. There is only one risk: if we delay with data/regulations, Bohdan will say "it doesn't work", and opponents will use the pause as a media argument. Therefore, I am taking control of the technical framework and signing off on KPI/measurement protocol, while maintaining communication with the transport company to coordinate courier movement windows.

Options

1. Officially launch the pilot analytics now: agree with Bohdan on the data collection protocol, pickup points, courier parking/entrance rules, and SLA, and only then...
2. Sit down with Pavlo Humeniuk regarding movement "windows" and intersections with city transport, to immediately reduce the risks of delays in microdistricts; simultaneously coordinate analytics...
3. Publicly announce the start of the "30 min" pilot and emphasize measurability, to intercept media campaigns around the embankment/coastal zone; technically coordinate in the background...

Choice. I choose option 1: without the SLA protocol and integration of pickup points, the pilot will turn into an experiment without results. Publicity makes sense only after the data and regulations are ready.

Diary. Today I set a course for the technical certainty of the 30-minute pilot: under the SLA/KPI protocol and the delay reasons matrix, I need to launch analytics and integration tags at 2 locations. Money – UAH 200,000 from my own funds for 6 weeks, so that the data is suitable for any city inspection. In parallel, I want to reduce traffic delay risks by coordinating "windows" with...

Outcome. Lytovchenko is preparing a delivery pilot with the "Kravets Market" network

World engine: UAH 200,000 of own funds for pilot analytics - within available money; requires Kravets' consent for logistics implementation.

Place: Saint Michael's Cathedral

Thoughts

The city is currently in a trust mode for environmental projects and modernizations, but logistics is what affects the daily comfort and real costs of businesses. It is important for me to ensure that in future city decisions, delivery is "built into" the rules: access points, entry schedule, standards for approaches, and SLAs. There is tension with Kravets, so I will not pressure the media: I will approach through technology and measurable conditions - I will offer him a partnership pilot with clear KPIs, where his network benefits, and the city gets controlled traffic flow. In parallel, I want to improve relations through a useful urban service, not through conflict.

Options

1. Propose a 6-week "30 min" pilot to Bohdan Kravets at 2 locations with a strict SLA, joint KPIs, and a report for city logistics; arrange courier access...
2. Contact the city architect Iryna Bondar with a proposal for a city standard "courier corridor/delivery hubs" within the current programs (without politics on...
3. Write to the editorial office of the newspaper "Chronicle 2046" and environmental blogs a short public manifesto on ecological logistics (fewer trips, faster collection/delivery), without mentioning...

Choice. I choose the first option: this is the fastest way to get data for city arguments and simultaneously relieve tension with Kravets through a pragmatic pilot with mutual benefit.

Diary. I am launching a move that is both beneficial to the city and saves my relationship with Kravets without emotions. The key is data: reasons for delays and a stable SLA. I hope to agree on delivery hubs and time slots so as not to disrupt the 30 minutes and gather material for future city proposals.